>  But is it clfs-1 or clfs-2 ?  Neve mind, in the light of your other
> responses I don't think we have anything to fix.

clfs-1


>> I found that the LFS book mentions that zlib doesn't build properly if
>> CFLAGS is set.  Definitely true.  It compiles properly if CFLAGS is
>> unset or if -fPIC is added to CFLAGS.  This comment should probably be
>> added to CLFS.
>>
>  -fPIC is an x86_64 requirement for mixing shared and static.  AFAIK
> no other architectures need it.  Anyway, if the book says that CFLAGS
> should NOT be set, that covers it.

Section 5.2 says that CFLAGS should not be set when building cross tools. 
The book doesn't mention CFLAGS when building the temporary or final
systems.  Now that I think of it, it's probably not worth setting it
during the temporary stage since this stage will be thrown away.

I'm not interested in having static libraries on my system, so I guess
-fPIC isn't needed.

>> The headers problem was caused by experimenting with config.site.  I
>> found that this package apparently ignores it and tries to install
>> into /usr/local, so --prefix cannot be omitted.
>>
>
>  So, you are deviating from the book.  I'll need to remember that
> and not immediately think we have something to fix.  I'm sure that
> other packages will ignore config.site (e.g. bzip2 does most things
> differently), so you will definitely need to keep an eye on what gets
> installed where.
>

I am deviating a bit while experimenting.  It helps me understand some of
the less obvious reasons LFS does certain things.  I didn't use
config.site for the cross toolchain, but I am for the temporary stage.

I experimented with --with-sysroot earlier.  It eliminates the need for a
few patches for some reason, but then gcc stupidly insists that headers
and libraries must be in usr if it is passed --with-sysroot.  I don't
really like the idea of putting glibc into usr without testing it first,
simply to satisfy gcc.  CLFS-2 does this and I am curious why.  CLFS-2 is
still under development, tho, so maybe it won't stay in there?

_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support

Reply via email to