From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: "Eric Bénard" <eric@eukrea.com>
Subject: Re: libXext-native fail to compile (x86_64)
Date: Thu, 25 Nov 2010 17:31:39 +0100 [thread overview]
Message-ID: <20101125163139.GQ3274@jama> (raw)
In-Reply-To: <4CEE6A7B.4010603@atmel.com>
On Thu, Nov 25, 2010 at 02:54:03PM +0100, Nicolas Ferre wrote:
> Le 25/11/2010 10:22, Eric Bénard :
> > Hi Nicolas,
> >
> > On 25/11/2010 09:56, Nicolas Ferre wrote:
> >> While trying to build from scratch the latest .dev branch with:
> >> - angstrom-2010.x distribution
> >>
> >> Build Configuration:
> >> BB_VERSION = "1.10.0"
> >> METADATA_BRANCH = "dev_for2010.12"
> >> METADATA_REVISION = "a1bba89"
> >> TARGET_ARCH = "arm"
> >> TARGET_OS = "linux-gnueabi"
> >> MACHINE = "at91sam9m10g45ek"
> >> DISTRO = "angstrom"
> >> DISTRO_VERSION = "next"
> >> TARGET_FPU = "soft"
> >>
> >>
> >> I have the following error with libxext:
> >> NOTE: package libxext-native-1_1.2.0-r9.0: task do_compile: Failed
> >>
> > it seems to build fine for others also on x86_64 host :
> > http://tinderbox.openembedded.net/packages/1077651/
> > http://tinderbox.openembedded.net/packages/1087310/
>
> Indeed, strange...
> I tried to clean the recipe and then rebuild without success.
> Someone has a hint where it can come from?
I've tried to reproduce on my 2 x86_64 hosts and both build it still
fine (both with gcc-4.5, SHR and micro)
But same problem was maybe reason here:
http://bugs.openembedded.org/show_bug.cgi?id=5490
but for him do_install failed.. weird
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-11-25 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 8:56 libXext-native fail to compile (x86_64) Nicolas Ferre
2010-11-25 9:22 ` Eric Bénard
2010-11-25 13:54 ` Nicolas Ferre
2010-11-25 16:31 ` Martin Jansa [this message]
2010-11-25 17:22 ` Nicolas Ferre
2010-11-28 9:39 ` Martin Jansa
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=20101125163139.GQ3274@jama \
--to=martin.jansa@gmail.com \
--cc=eric@eukrea.com \
--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