From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Danny Gale <Daniel.Gale@coloradoengineeringinc.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Potential bug in 1.19.0
Date: Thu, 09 Jan 2014 22:50:00 -0000 [thread overview]
Message-ID: <20140109225005.GF3713@free.fr> (raw)
In-Reply-To: <52CCBBE2.6060207@coloradoengineeringinc.com>
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.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-01-09 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 2:45 Danny Gale
2014-01-08 3:19 ` Bryan Hundven
2014-01-09 21:42 ` Danny Gale
2014-01-09 22:50 ` Yann E. MORIN [this message]
2014-01-10 18:05 ` Danny Gale
2014-01-10 18:08 ` Danny Gale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140109225005.GF3713@free.fr \
--to=yann.morin.1998@free.fr \
--cc=Daniel.Gale@coloradoengineeringinc.com \
--cc=crossgcc@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).