From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: glibc_2.9 compile failed for armv5te
Date: Fri, 16 Oct 2009 13:03:55 +0200 [thread overview]
Message-ID: <4AD8531B.6070208@dresearch.de> (raw)
In-Reply-To: <4AD59AF2.50003@dresearch.de>
Steffen Sledz wrote:
> Since a few days a clean build of glibc_2.9 failed for hipox machine
> (armv5te) with this error (details see attached logfile):
>
> | ../ports/sysdeps/arm/eabi/setjmp.S: Assembler messages:
> | ../ports/sysdeps/arm/eabi/setjmp.S:45: Error: internal_relocation
> (type: OFFSET_IMM) not fixed up
>
> Sorry, but i've no idea what the problem is and which commit is
> responsible for it. Any ideas?
My tries to identifiy the commit responsible to this problem drive me
crazy. Everytime i thought i'de catched the causer a recheck brought a
different result. :(
So i updated to the HEAD (commit
9a6a9e12a1ef50296621c2eea9fe385464b64f02) and tried again. And really
it seems that the behaviour is not deterministic:
-----------------------------------------------------------
# rm -rf tmp.3
# bitbake glibc
--> everything worked well :)
-----------------------------------------------------------
# rm -rf tmp.3
# bitbake glibc
--> failed with something like "sed: can't read
/home/DRESEARCH/sledz/work/HydraIP/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r35.2/build-arm-angstrom-linux-gnueabi/tcb-offsets.h.dT:
No such file or directory" :(
# bitbake glibc
--> succeeded ???
-----------------------------------------------------------
# rm -rf tmp.3
# bitbake glibc
--> failed with something like "sed: can't read
/home/DRESEARCH/sledz/work/HydraIP/OE/tmp.3/work/armv5te-angstrom-linux-gnueabi/glibc-2.9-r35.2/build-arm-angstrom-linux-gnueabi/tcb-offsets.hT3:
No such file or directory" :(
# bitbake glibc
--> succeeded ???
-----------------------------------------------------------
Any ideas? Can somebody reproduce this behaviour? A bitbake problem?
Steffen
next prev parent reply other threads:[~2009-10-16 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 9:33 glibc_2.9 compile failed for armv5te Steffen Sledz
2009-10-14 10:32 ` Phil Blundell
2009-10-14 12:31 ` Steffen Sledz
2009-10-14 16:58 ` Khem Raj
2009-10-16 6:29 ` Steffen Sledz
2009-10-16 11:03 ` Steffen Sledz [this message]
2009-10-16 14:02 ` Steffen Sledz
2009-10-16 14:20 ` Roman I Khimov
2009-10-16 14:27 ` Steffen Sledz
2009-10-16 14:45 ` Phil Blundell
2009-10-16 14:51 ` Steffen Sledz
2009-10-16 20:54 ` Khem Raj
2009-10-16 21:07 ` Andrea Adami
2009-10-19 8:46 ` Steffen Sledz
2009-10-19 10:04 ` Andrea Adami
2009-10-19 10:26 ` Steffen Sledz
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=4AD8531B.6070208@dresearch.de \
--to=sledz@dresearch.de \
--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