From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure building gcc-cross-initial for armv5te
Date: Wed, 20 Oct 2010 18:26:01 +0200 [thread overview]
Message-ID: <i9n56p$ppm$1@dough.gmane.org> (raw)
In-Reply-To: <4CBF01C6.7030409@gravedo.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20-10-10 16:50, Simon Busch wrote:
> On 20.10.2010 16:05, Martin Jansa wrote:
>> On Wed, Oct 20, 2010 at 09:26:32AM -0400, Nik wrote:
>>> What os are you compiling on? Can you run the cross compile gcc from the command line and get the no input files message?
>>
>> Related log from #oe - as I'm lazy to type it again :)
>>
>
> As I tried a little bit more I tracked it down to the commit
> f1148d26740e57cba4fe29fd78c234359868a50e ("binutils.inc: Filter out
> --with-sysroot for target binutils"). If you revert this one and do a
> fresh build (rm -rf tmp) everything compiles fine.
It would be nice if commits like that bumped PR so problems also show up
in incremental builds. And in this case, the fixed *packages* can end up
in the feeds.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMvxgZMkyGM64RGpERAnirAKCvfFOmzQTOqYTS5+PxFUFHzxHDrwCgonk2
PxM2Xi/EQa0uma+SY+F1LmI=
=B1wz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-10-20 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 9:35 failure building gcc-cross-initial for armv5te Jaap de Jong
2010-10-20 10:35 ` Holger Freyther
2010-10-20 10:37 ` Gary Thomas
2010-10-20 11:25 ` Frans Meulenbroeks
2010-10-20 11:33 ` Gary Thomas
2010-10-20 13:26 ` Nik
2010-10-20 14:05 ` Martin Jansa
2010-10-20 14:50 ` Simon Busch
2010-10-20 16:26 ` Koen Kooi [this message]
2010-10-20 17:18 ` Khem Raj
2010-10-20 18:31 ` Andreas Oberritter
2010-10-20 19:21 ` Khem Raj
2010-10-20 14:43 ` Jaap de Jong
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='i9n56p$ppm$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.