From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: Bryan Hundven <bryanhundven@gmail.com>,
Chris Wilkinson <winstonian36@gmail.com>
Subject: Re: CT-NG v1.14.0 Build Fails
Date: Wed, 01 Feb 2012 21:08:00 -0000 [thread overview]
Message-ID: <201202012207.46569.yann.morin.1998@free.fr> (raw)
In-Reply-To: <CAJ+oik1ne4EMzNLX0EWnoAyDouz2C7WiVSOJHBc8ra9oY7OuEg@mail.gmail.com>
Chris, Bryan, All,
On Wednesday 01 February 2012 20:46:33 Bryan Hundven wrote:
> On Wed, Feb 1, 2012 at 11:38 AM, Chris Wilkinson <winstonian36@gmail.com> wrote:
> > Fails at step cc_core_pass_2. Using the sample config
> > 'powerpc-e300c3-linux-gnu'.
That sample built fine yesterday before I did the release.
Host: Debian Squeeze x86_64
I'm rebuilding right now to double-check, though...
> Could you post a full build.log somewhere. Please don't attach it to
> the ML, as it is too big.
> Also, I know it is a sample config, but it may be outdated and before
> the build ct-ng runs 'oldconfig' which changes the config. If you
> could also post the config from your build directory, that could also
> prove useful.
What you said made me think about it, and you are right. Even if the sample
is up-to-date with the option set, if the host is missing some dependencies
which were present on my system, then the local .config can indeed be
different.
If this is the case, then 'oldconfig' would prompt the user, so it would
have been noticed...
But indeed: build.log (compressed) on some http site, and local .config
would help to solve the issue.
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:[~2012-02-01 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 19:39 Chris Wilkinson
2012-02-01 19:46 ` Bryan Hundven
2012-02-01 21:08 ` Yann E. MORIN [this message]
2012-02-02 3:22 ` Chris Wilkinson
2012-02-02 15:12 ` Chris Wilkinson
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=201202012207.46569.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=winstonian36@gmail.com \
/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).