./configure, CFLAGS, checkinstall, and kernel arch type
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.
./configure, CFLAGS, checkinstall, and kernel arch type
hi,
i use kernel 2.6.9 with the processor as pentium m (centrino). i believe that is i686. when i used checkinstall on a compiled app, it displayed "i386." echo $CFLAGS returns nothing. does that mean if i just do the default ./configure, i will not get the binaries that are optimized for my computer? shouldn't CFLAGS use the setting from the kernel?
anyway, i then tried
Code:
CFLAGS="-march=i686 -O2 -pipe" ./configure
so during make, i could see that gcc was called with the -march=i686 flag. however, checkinstall still displayed "i386." i'm guessing checkinstall is wrong, and the compiled binaries are optimized for my computer.
thanks.
Checkinstall doesn't detect anything - it just sets the default name - check /etc/checkinstall/checkinstallrc and change ARCHITECTURE. 'echo $CFLAGS' should only produce something if you've exported that to the environment for general compiling. But, yeah, if gcc was picking it up, it's all good.
Originally posted by digiot 'echo $CFLAGS' should only produce something if you've exported that to the environment for general compiling.
i think i will export CFLAGS. it seems like a good idea, and i believe it's not going to cause any harm (because gentoo has it in /etc/make.conf for all compilations--i believe). if anyone sees anything wrong/dangerous with my thinking, please point it out.
thanks.
Well, mplayer likes to make up its own flags and there may be another program or two that doesn't like it, but it's easier to unset it on the rare exception that constantly set it for most things. So AFAIK, it's a good plan. (I do it, anyway. )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.