On 3/5/12 6:57 PM, Qrux wrote:
>
> On Mar 4, 2012, at 7:10 AM, Jeremy Huntwork wrote:
>
>> On 3/1/12 4:27 PM, Jeremy Huntwork wrote:
>>> And because of the pre-adjusting there's even less chance to bring in
>>> something from the host system. The limits.h file is an example. The
>>> first pass of GCC doesn't install a full-featured limits.h file because
>>> it can't find one in the include paths we've specified.
>>
>> One more thing. Because of tightly controlling where the compiler
>> searches for headers, etc, the statement about the adjustment for the
>> fixincludes script in pass 2 does not appear to be true any more:
>>
>> It says "In fact, running this script may actually pollute the build
>> environment by installing fixed headers from the host system into GCC's
>> private include directory."
>
> For the gcc-bootstrapping in general, is there any "validation" whether host
> files are getting improperly included at various stages of the build (e.g., a
> real simple md5sum-type thing) in either the existing method or the
> --with-sysroot method?
'real simple md5sum-type thing'... not that I'm aware of. The most
telling bits are when you add verbosity to the compiler and linker flags
and examine the output, see where it's searching, e.g.:
printf '#include <limits.h>\nint main(){ return SSIZE_MAX; }' | \
$LFS_TGT-gcc -x c - -v -Wl,--verbose -lrt -lm -lpthread
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
