From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: oe for two target boards at the same time
Date: Tue, 9 Oct 2007 13:49:29 +0200 [thread overview]
Message-ID: <20071009134929.0ebdf0ce@aquilonia> (raw)
In-Reply-To: <20071009131812.0f55c4d2@aquilonia>
On Tue, 9 Oct 2007 13:18:12 +0200
Graeme Gregory <dp@xora.org.uk> wrote:
> On Tue, 09 Oct 2007 12:36:22 +0200
> Richard Purdie <rpurdie@rpsys.net> wrote:
> > The issue should be fixed. I regularly make builds with a MACHINE ?=
> > entry but with MACHINE set in the environment too and it all seems
> > to work.
> >
> > People keep telling me there is a problem but I've not seen any
> > reproducible test case...
> >
>
> NOTE: package binutils-cross-2.18-r0: task do_populate_staging:
> completed
>
> looks fixed to me, I never used to be able to do this.
>
Spoke too soon
checking for libc-friendly stddef.h... yes
checking whether we need to use -P to assemble .S files... no
checking whether .text pseudo-op must be used... yes
checking for assembler global-symbol directive... .globl
checking for .set assembler directive... no
checking for assembler .type directive prefix... %
checking for .symver assembler directive... yes
checking for ld --version-script... no
*** WARNING: You should not compile GNU libc without versioning. Not
using *** versioning will introduce incompatibilities so that old
binaries *** will not run anymore.
*** For versioning you need recent binutils (binutils-2.8.1.0.23 or
newer). checking for .previous assembler directive... yes
checking for .protected and .hidden assembler directive... yes
checking whether __attribute__((visibility())) is supported... yes
checking for broken __attribute__((visibility()))... no
checking for broken __attribute__((alias()))... no
checking whether to put _rtld_local into .sdata section... no
checking for arm-angstrom-linux-gnueabi-readelf...
arm-angstrom-linux-gnueabi-re adelf
checking for .preinit_array/.init_array/.fini_array support... no
configure: error: Need linker with .init_array/.fini_array support.
FATAL: oe_runconf failed
This is what happens if MACHINE=spitz bitbake angstrom-devel-image
Graeme
next prev parent reply other threads:[~2007-10-09 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 10:41 hello Tobias Pflug
2007-10-04 11:18 ` hello Michael Krelin
2007-10-04 12:40 ` hello Holger Freyther
2007-10-04 12:55 ` monotone/git (was hello...) Tobias Pflug
2007-10-04 13:27 ` Holger Freyther
2007-10-04 13:50 ` Darcy Watkins
2007-10-04 13:52 ` Michael Krelin
2007-10-05 6:28 ` oe for two target boards at the same time Alex
2007-10-05 13:57 ` Cliff Brake
2007-10-05 15:47 ` Khem Raj
2007-10-06 8:19 ` Koen Kooi
2007-10-06 11:39 ` Marcin Juszkiewicz
2007-10-08 20:20 ` Cliff Brake
2007-10-09 8:28 ` Koen Kooi
2007-10-09 9:02 ` pHilipp Zabel
2007-10-09 10:36 ` Richard Purdie
2007-10-09 11:18 ` Graeme Gregory
2007-10-09 11:49 ` Graeme Gregory [this message]
2007-10-09 16:52 ` Paul Sokolovsky
2007-10-09 16:48 ` Paul Sokolovsky
2007-10-04 18:02 ` monotone/git (was hello...) Richard Purdie
2007-10-04 13:51 ` Michael Krelin
2007-10-04 13:30 ` Michael Krelin
2007-10-04 18:36 ` Chris Larson
2007-10-04 18:49 ` Tim Bird
2007-10-04 18:57 ` Chris Larson
2007-10-04 19:11 ` Michael Krelin
2007-10-04 19:27 ` Chris Larson
2007-10-04 19:39 ` Michael Krelin
2007-10-04 20:18 ` Chris Larson
2007-10-04 20:53 ` Michael Krelin
2007-10-04 19:08 ` Michael Krelin
2007-10-04 19:28 ` Chris Larson
2007-10-04 13:19 ` hello Michael Krelin
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=20071009134929.0ebdf0ce@aquilonia \
--to=dp@xora.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox