SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
gnashley, I received your email with the attached file, and replaced the existing 01-pre process file with this one. I compiled a few programs and I did not notice any errors in relation to the previous version of src2pkg. Among one of the packages I used src2pkg on, both before and after the file replacement, was for FileZilla. Here is the output from the package compilation using src2pkg 1.9.4 w/ new file:
Code:
root@slack-deathstar:/home/swampdog/Downloads# src2pkg FileZilla_3.0.6_src.tar.bz2
Notice - Source name contains capital letters.
Resetting package name - Using: filezilla_3.0.6
Found source archive: FileZilla_3.0.6_src.tar.bz2
Deleting old build files - Done
Creating working directories:
PKG_DIR=/tmp/filezilla_3.0.6-src-pkg-1
SRC_DIR=/tmp/filezilla_3.0.6-src-src-1
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - None found
Found configure script - Configuring sources using:
CFLAGS=-O3 -march=athlon-xp -pipe -fomit-frame-pointer ./configure --prefix=/usr
Configuration has been - Successful!
Compiling sources - Using: 'make'
Compiling has been - Successful!
Installing in jail root - Using: 'make install'
Safe installation - Successful!
Processing package content:
Correcting package permissions - Done
Stripping ELF binaries - Done
Checking for standard documents - Done
NOTICE! Moving man pages installed under usr/share/man to usr/man
Compressing man pages - Done
Creating slack-desc - Creating slack-desc file in PKG_DIR
Copying slack-desc to: new.slack-desc in CWD.
The files new.slack-desc (and new.slack-required) are copies
of the slack-desc (and slack-required) files inserted in the
package. If you want to change the content, edit and then
save the files as simply slack-desc (and slack-required).
Otherwise, they are re-created when you repeat the build.
Searching for links in PKG_DIR - None found
Making installable package - Done
Package Creation - Successful! - Package Location:
/tmp/filezilla_3.0.6-src-athlon_xp-1.tgz
Last edited by swampdog2002; 02-06-2008 at 07:29 PM.
Yeah, Tim is right. This is not good:
Resetting package name - Using: filezilla_3.0.6
(this means that the version is 'src'. These errors with name and vesrion are not dangerous, but it will keep upgradepkg from working properly.
This will fix that problem
src2pkg -n=filezilla -v=3.0.6 FileZilla_3.0.6_src.tar.bz2
Otherwise, thanks very much for testing the new CFLAGS code -it seems to be working as expected. Only time will tell if those options are really the best ones to use -I can imagine that -O3 might be a problem for some compiles, but maybe not.
So if you ever have problems with this let me know. I also have doubts about whether to set the ARCH=athlon_xp by default for packages compiled this way. I believe that such packages should run alright on regular ix86 machines so it may not be desirable to name them with ARCH=athlon_xp. If you don't like this you can alwas specify the ARCH (with -a=i486). I'm interested in what you, the users, think about this so that I can set default values which are agreeable to the users whenever it seems to be a harmless matter of preference.
Thanks again!
Tested your new addition, and it works just like the file that was replaced.
The packages that worked before work now, and the packages that I was inadequate for, well I am still inadequate.
The only problems that I have had were caused by my lack of knowledge. So I have dug out my old university notes on shell programming and begun revising.
You can always use -mtune=native if you really only need the result to run on one specific cpu (being the same type it was build on).AFAIK this option was introduced with gcc 4.0 - was the first time I got aware of it anyway.
native
This selects the CPU to tune for at compilation time by determining the processor type of the compiling machine. Using -mtune=native will produce code optimized for the local machine under the constraints of the selected instruction set. Using -march=native will enable all instruction subsets supported by the local machine (hence the result might not run on different machines)
The -Os (size optimized)switch is normally safer to use than -O3 if you just compile everything with the same switch - it enables all the O2 options minus the ones that increase size.The result should still be plenty fast and the load time decreases because the binary is optimized for size.
To get the last drop of performance out of databases and the likes you'll need to set specific options anyway.
Yeah, Tim is right. This is not good:
Resetting package name - Using: filezilla_3.0.6
(this means that the version is 'src'. These errors with name and vesrion are not dangerous, but it will keep upgradepkg from working properly.
This will fix that problem
src2pkg -n=filezilla -v=3.0.6 FileZilla_3.0.6_src.tar.bz2
Thanks. I was wondering why I had problems with launching the application after I had installed this with installpkg. For some reason, I received a message stating that FileZilla was unable to access the data directory, and that I needed to set a specific variable to point to this location. I'll give this another attempt with the switches -n and -v.
swampdog2002, That runtime error sounds like something else. You may need to pass something to the configure script. I quickly downloaded the sources to see what options are avialable. Looks like this may be what you need: --datarootdir=/usr/share
You can tell src2pkg to pass that to configure by using this -e='--datarootdir=/usr/share' along with the already mentioned options for correcting the name and version.
Thanks for everyone who has replied and tested. Thanks especially to brianL and crashmeister for the excellent links on the subject.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.