From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Question: is 'gcc' supposed to replace the libstdc++.la installed by 'gcc-cross'?
Date: Mon, 17 May 2010 11:38:03 +0200 [thread overview]
Message-ID: <hsr2pr$4vp$1@dough.gmane.org> (raw)
In-Reply-To: <20100517055550.GA6686@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-05-10 07:55, Khem Raj wrote:
> On (17/05/10 07:44), Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> I just noticed that after doing 'bitbake gcc' the old libstdc++ gets
>> replaced and the new one has:
>>
>> dependency_libs='
>> /OE/angstrom-dev/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/libstdc++.la'
>>
>> instead of the expected '-lm'. It now refers to itself :(
>
> hmmm target gcc should not have staged libstdc++ if it was already staged
> by gcc-cross but the problem is casued by
> gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch it passed the native libdir which
> is build_libdir even for target library builds using -rpath. I am currently
> looking into the reason. If possible we can get rid of that patch.
I'm getting a build failure with 'gcc' now failing to find libstc++.la.
I'm trying a build from scratch now to rule out any packaged-staging
problems (>1 recipes installing the same file, pstage removing it prior
to build).
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL8Q57MkyGM64RGpERAvvpAJ4vR4wtskIhV6BBUN/LcOzxXYPSEwCeNNtm
FWhLXTLoZUXa+yIDjlEiNbo=
=EvPm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-17 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 5:44 Question: is 'gcc' supposed to replace the libstdc++.la installed by 'gcc-cross'? Koen Kooi
2010-05-17 5:55 ` Khem Raj
2010-05-17 9:38 ` Koen Kooi [this message]
2010-05-17 13:52 ` Koen Kooi
2010-05-17 16:49 ` Khem Raj
2010-05-17 17:02 ` Koen Kooi
2010-05-17 17:45 ` Khem Raj
2010-05-17 18:12 ` Tom Rini
2010-05-17 18:52 ` Khem Raj
2010-05-20 13:39 ` Phil Blundell
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='hsr2pr$4vp$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.