Question regarding compiling packages
Bill Maltby - LFS Related
lfsbill at wlmcs.com
Sat Nov 2 09:16:52 PST 2002
On Sat, 2 Nov 2002, Jamie wrote:
> I was wondering if anyone can explain why some of the packages for
>lfs are compiled with options set in configure, while other packages are
>compiled with certain options set in "make". For example, two different
>packages used in lfs, file-utils and gzip, each pass the argument
>LDFLAGS=-static, but file-utils does it when configure runs, and gzip does
>it when make is performed. Here is a snapshot:
> LDFLAGS=-static \
> ./configure --disable-nls --prefix=$LFS/static &&
> make &&
> make install
> --above you can see that LDFLAGS is set before configure runs.
> ./configure --prefix=$LFS/static &&
> make LDFLAGS=-static &&
> make install
> --in this example LDFLAGS is set when make is run.
> Why is there a difference between the two? Does the sequence even
>matter and one just happened to be set in one location while the other was
>set differently, or does it really matter and if so why?
> I was looking into some tutorials on the Net which cover autoconf and
>make, but none of them seemed to point out the answer to my question.
Because some packages are faulty and do not get the flags from the
configure process (and some do) but do use the environmental variable.
There is a thread on this (use the LFS search of the archives) that
explains the details.
> - Jamie
billm at wlmcs.com
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message
More information about the lfs-support