Yann, All,

Here's my config file. For what it's worth, I believe now that this is a 
problem with GCC, not Crosstool-NG. I'm attempting a fix similar to the 
patch here (http://gcc.gnu.org/ml/gcc/2009-07/msg00082.html)

Thanks,
Danny

On 01/09/2014 03:50 PM, Yann E. MORIN wrote:
> Danny, All,
>
> On 2014-01-07 19:45 -0700, Danny Gale spake thusly:
>> 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/
> Can you provide your .config, please, so I can try to reproduce it here?
>
> Regards,
> Yann E. MORIN.
>