Hello,
I don't have o.dummy file so I removed that so I reduced the command to
gcc -v dummy.c 2>&1 | tee dummy-output
I noticed 3 lines there that doesn't seem make sense to me and which is probably the cause of the error
One line says ignoring nonexistent directory
"/mnt/lfs/tools/bin /../lib/gcc/i686-pc-linux-gnu/3.4.1/../../../../i686-pc-linux-gnu/include"
Well that's probably true I don't have a directory with all those /../
But if gcc was smart enough to find the path in there I don't think I would be having this problem The specs file is right after the 3.4.1 in that path
so if it says that the directory is non existent I don't see how it can find the file in a nonexistent directory
the second line says ignoring duplicate directory
"/tools/lib/gcc/i686-pc-linux-gnu/3.4.1/include"
Well if it's talking about "i686-pc-linux-gnu" then yes there is 2 of them only in the path above but in reality there is only one directory
The third line says once again ignoring nonexistent directory
"tools/lib/gcc/i686-pc-linux-gnu/3.4.1/../../../../i686-pc-linux-gnu/include"
That's just a different version of the first line
That's what my suspicion was when I first saw the /../
Is there a way to force gcc use absolute path ?
|