Opened 19 years ago
Closed 19 years ago
#1768 closed defect (fixed)
Sanity checks don't work after final GCC
Reported by: | Jeremy Huntwork | Owned by: | Jeremy Huntwork |
---|---|---|---|
Priority: | normal | Milestone: | 6.2 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
See this original thread:
http://linuxfromscratch.org/pipermail/lfs-dev/2006-March/056423.html
Apart from the issue in the summary, we could probably stand to extend the sanity checks a bit further.
Change History (3)
comment:1 by , 19 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 19 years ago
Note:
See TracTickets
for help on using tickets.
Just as a pointer to keep the mailing list posts in tracked, here is a more recent post about a necessary fix:
http://linuxfromscratch.org/pipermail/lfs-dev/2006-April/056800.html
I'd like to ammend that proposal a bit. Put a / in front of crt so you know you're getting startfiles (not that I know of anything else that would be caught). Then, I propose changing the Re-Adjusting check to:
$ grep '/usr/lib.*/crt[1in].o ' dummy.log
or
$ grep '/usr/lib.*/crt1.o ' dummy.log
One other thing that I didn't mention in either post is that we never check to see if the ld adjustment has actually been correct. Since ld is almost always invoked by gcc, this sanity check would work:
$ grep 'SEARCH.*/usr/lib' dummy.log
This assumes -Wl,--verbose is issued. /tools could be substituted in Adjusting. Alternatively, to check ld without actually compiling anything, you can use this command:
$ $(cc -print-prog-name=ld) --verbose | grep 'SEARCH.*/usr/lib'