From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Images no longer automatically include libstdc++6
Date: Sat, 11 Sep 2010 09:09:18 +0200 [thread overview]
Message-ID: <i6f9uu$39o$1@dough.gmane.org> (raw)
In-Reply-To: <4C8ADB7A.4000303@techsol.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-09-10 03:29, Dallas Foley wrote:
> On 10-09-08 07:33 AM, Philip Balister wrote:
>> On 09/08/2010 10:09 AM, pieterg wrote:
>>> On Tuesday 07 September 2010 21:03:14 Koen Kooi wrote:
>>>> On 07-09-10 18:18, Khem Raj wrote:
>>>>> On Tue, Sep 7, 2010 at 5:52 AM, Koen Kooi<k.kooi@student.utwente.nl>
>>> wrote:
>>>>>> it happens when you build 'gcc' after 'gcc-cross', gcc will doesn't
>>>>>> create a libstdc6++ package, but it does create a libstdc-dev
>>>>>> package.
>>>>>
>>>>> I see thats plausible. I think its time to look into separating gcc
>>>>> runtime from gcc on the lines of poky.
>>>>
>>>> I put back libgcc and libstdc++ for the time being:
>>>>
>>>> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=241b8865f20
>>>>
>>>> b9e3c3beb334535e6cd8452cbf47d
>>>>
>>>> I have a feeling the others needs to put back as well (e.g. fortran),
>>>> but this fixes the immediate problem.
>>>
>>> Not for me, after a clean build today packages are still missing
>>> libstdc++
>>> in their deps (and as a result the images are still missing libstdc++).
>>> So there must be more to it.
>>
>> Does anyone have any idea what commit caused this breakage? It is
>> causing a lot
>> of problems for people.
>>
>> Philip
>
> With git bisect I get commit d2a283ad002660e46b2f8d40a8ddfabad457d8a4
> that causes libstdc++ to not get included.
Yep, that's the one:
./x86_64-linux/shlibs/libssp.ver
./x86_64-linux/shlibs/libstdc++.ver
./x86_64-linux/shlibs/libgfortran.list
./x86_64-linux/shlibs/libssp.list
./x86_64-linux/shlibs/libstdc++.list
./x86_64-linux/shlibs/libgfortran.ver
./x86_64-linux/shlibs/libgcc.list
./x86_64-linux/shlibs/libgcc.ver
For gcc we probably need to add the following to gcc.inc:
SHLIBSDIR = "${STAGING_DIR}/${BASEPKG_HOST_SYS}/shlibs"
That should put the shlibs back where they belong for gcc.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMiyseMkyGM64RGpERAmS7AKC2VvzfFIzXTYKmgkMm2CF8olPvGACfcM48
XTf/BdxREFQe5KBQnVH/lbw=
=vEE1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-09-11 7:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 22:21 Images no longer automatically include libstdc++6 Steve Sakoman
2010-09-06 22:52 ` J. L.
2010-09-07 5:54 ` Khem Raj
2010-09-07 8:20 ` J. L.
2010-09-07 12:52 ` Koen Kooi
2010-09-07 16:18 ` Khem Raj
2010-09-07 19:03 ` Koen Kooi
2010-09-08 6:01 ` Frans Meulenbroeks
2010-09-08 14:09 ` pieterg
2010-09-08 14:33 ` Philip Balister
2010-09-11 1:29 ` Dallas Foley
2010-09-11 7:09 ` Koen Kooi [this message]
2010-09-11 7:46 ` patch to fix libstdc++ problem, was " Koen Kooi
2010-09-12 8:34 ` Frans Meulenbroeks
2010-09-12 9:11 ` Koen Kooi
2010-09-12 11:27 ` Frans Meulenbroeks
2010-09-12 11:48 ` Koen Kooi
2010-09-12 12:11 ` Frans Meulenbroeks
2010-09-12 12:27 ` Philip Balister
2010-09-12 12:49 ` Frans Meulenbroeks
2010-09-12 13:04 ` Philip Balister
2010-09-12 13:23 ` Frans Meulenbroeks
2010-09-12 18:52 ` Koen Kooi
2010-09-13 6:23 ` Frans Meulenbroeks
2010-09-13 7:22 ` Graham Gower
2010-09-12 21:08 ` pieterg
2010-09-12 23:56 ` dfoley
2010-09-13 6:01 ` Khem Raj
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='i6f9uu$39o$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.