This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See crosstool-NG for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Potential bug in 1.19.0


My build is currently failing with "./config/rs6000/linux64.h: No such file or directory". The call generating this error is: build/gengtype -S /path/to/working/dir/src/gcc-4.7.2/gcc -I gtyp-input.list -w tmp-gtype.state

Which is being called from the directory: /path/to/working/dir/powerpc64-e6500-linux-gnu/build/build-cc-core-pass-1/gcc/

Looking at the file gtyp-input.list in that directory, all the other paths in that file are absolute paths, while the path to the "missing" file is relative. Why is this the case? Is this a bug in gcc or Crosstool-NG? How can it be fixed?

The relative path should be relative to /path/to/working/dir/src/gcc-4.7.2/ instead of /path/to/working/dir/powerpc64-e6500-linux-gnu/build/build-cc-core-pass-1/gcc/

Thanks,
Danny

--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]