From: Tim Sander <tim@krieglstein.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] glibc error with arm-1136jfs-linux-gnueabihf
Date: Tue, 29 Jan 2013 09:29:01 +0100 [thread overview]
Message-ID: <2901611.D3YEXqgAbT@dabox> (raw)
In-Reply-To: <20130125164024.GB11534@pengutronix.de>
Hi Michael
> On Fri, Jan 25, 2013 at 04:34:14PM +0100, Tim Sander wrote:
> > > ld-linux-armhf.so.3 is correct but gcc reports the wrong name.
> > > This is a bug in the toolchain. It's fixed in git and I'm currently
> > > collecting other issued that I want to fix for a 2012.12.1 release.
> >
> > Mh, i have just compiled the git repository
> > git://git.pengutronix.de/git/OSELAS.Toolchain.git and the fix is not in
> > there? But i can also wait for next release...
>
> It should be there in the master branch. What commits do you see since the
> release? What do you get if you try this:
>
> echo 'int main() { return 0; }' \
>
> | arm-1136jfs-linux-gnueabihf-gcc -x c -v -o /dev/null - \
> |
> |& sed -n 's:.*-dynamic-linker \([^ ]*\) .*:\1:p'
>
> I'm getting "/lib/ld-linux-armhf.so.3" here now. With the release I got
> "/lib/ld-linux.so.3".
Its the new one but due to the earlier error i had some stale rule files for
testing which i forgot due to the intermittent testing on this. So its
compiling right now, better yet it even works :-) which was not the case for
the 2011.11.3 toolchain for unkown reasons.
Thanks
Tim
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-01-29 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 23:10 Tim Sander
2013-01-24 7:40 ` Michael Olbrich
2013-01-25 15:34 ` Tim Sander
2013-01-25 16:40 ` Michael Olbrich
2013-01-29 8:29 ` Tim Sander [this message]
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=2901611.D3YEXqgAbT@dabox \
--to=tim@krieglstein.org \
--cc=ptxdist@pengutronix.de \
/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