Jeremy Huntwork wrote:
> Now for the debugging...
Well, this is forcing me to read up about gcc internals.
The error is occurring when building for stage3. First impression is
that there is difficulty processing the specs file. You can truncate the
specs file (located in ./gcc/specs) or point xgcc to use an empty file
with the '-specs' flag and the same 'specs: Invalid argument' error
appears. However, if you delete the specs file entirely and don't
provide an alternate, forcing xgcc to use its built-in specs, this error
shows up:
$ echo 'main(){}' | ./gcc/xgcc -xc -v -
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.2.1/configure --prefix=/tools
--with-local-prefix=/tools --disable-nls --disable-shared
--enable-languages=c --disable-multilib
Thread model: posix
gcc version 4.2.1
cc1 -quiet -v -iprefix
/mnt/lfs/sources/gcc-build/gcc/../lib/gcc/x86_64-unknown-linux-gnu/4.2.1/
- -quiet -dumpbase - -mtune=generic -auxbase - -version -o /tmp/ccDiOCyh.s
xgcc: error trying to exec 'cc1': execvp: No such file or directory
I'm not exactly sure how cc1 is meant to be used, but running it
directly without any arguments produces some worrying results:
$ ./gcc/cc1
cc1: error: /tools/include: Invalid argument
cc1: error: /tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.1/include:
Invalid argument
cc1: error: /tools/lib/../x86_64-unknown-linux-gnu/include: Invalid argument
cc1: error: /usr/include: Invalid argument
cc1: error: stdout: Invalid argument
Going to have to do some more reading on how cc1 is employed, and the
order in which things are done when gcc compiles a file.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
