LFS7.2, problem when chapter 6.10: adjusting the toolchain, can not change gcc specs
Hi guys.
I meet a weired problem. I'm just finishing chapter 6.9 glibc-2.16.0, now I need to adjust my toolchain. Here is the code from book I run: Code:
gcc -dumpspecs | sed -e 's@/tools@@g' \ Quote:
Quote:
Quote:
Does anyone has any idea? Thank you. |
Maybe I'm still half asleep, but what is the actual problem?
The first gcc -dumpspecs command you posted is changed by sed and put in a file and the second gcc -dumpspecs command you post is just the bare, unchanged output. |
Hi, druuna, thanks for your reply.
Here is the problem, the gcc -v says gcc is using the specs file created by first gcc -dumpspecs and sed command, but the second gcc -dumpspecs still prints out unchanged specs. Should this be a problem? or gcc -dumpspecs just always gives original built-in specs? |
IIRC there is nothing in the book on running gcc -dumpspec twice to verify, do the other tests to verify the toolchain. if they are not correct then there is a problem, but if the tests works then there is no problem and correct specs are used.
|
Quote:
gcc -dumpspecs prints all of the built in spec strings. gcc will use the spec file when doing its thing. |
Quote:
I'm test toolchain following chapter 6.10 in LFS7.2: Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
next test libc: Quote:
Quote:
Quote:
Quote:
Can you see what's wrong here? Thank you. |
Quote:
I do find it curious that half the entries are correct (no /tools) and the other half does have the (incorrect) /tools part. Never seen that before. |
Quote:
I had a similar problem. What worked for me was to break it down into pieces. I did a gcc -dumpspecs > specs.org before the sed. Then I did another gcc -dumpspecs and piped that through the first sed, and sent that to sed.out. Then the second sed on sed.out > sed2.out. Then the third sed on sed2.out > sed3.out. Then copied sed3.out into the specs file. After each step I diffed the output against the original specs file (specs.orig) to see if there were any changes and if the changes made sense. If they all do, then look at gcc --print-libgcc-filename, and make sure that makes sense as well, although I can't imagine how anything would work if that was wrong. |
All times are GMT -5. The time now is 07:29 AM. |