Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch to fix libstdc++ problem, was Re: Images no longer automatically include libstdc++6
Date: Sun, 12 Sep 2010 13:48:14 +0200	[thread overview]
Message-ID: <i6ielv$sld$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTinELVSoGrq1km6dFpXGF524h328t+TBM4p32inz@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12-09-10 13:27, Frans Meulenbroeks wrote:
> 2010/9/12 Koen Kooi <k.kooi@student.utwente.nl>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 12-09-10 10:34, Frans Meulenbroeks wrote:
> 
>>> Haven't had time to test this yet, but I feel at least a PR bump is
>>> missing (or perhaps a set of PR bumps)
>>
>> Since it would require a PR bump for everything that is built with gcc,
>> I'm going to say:
>>
>> That's what DISTRO_PR is for, which is up to distro maintainers to bump.
> 
> Still I feel PR or INC_PR bumps of the affected gcc recipes is
> appropriate, if only to fix it for distro's that do not immediately
> bump DISTRO_PR.
> We have quite some distro's and not all are maintained equally well,
> so I can imagine it'll take some time for them to bump
> Actually some distro's seem orphaned, so for those it might never
> happen and bumping the GCC PR's at least will give them the fix too.

It won't, since you need to rebuild everything that uses gcc. Bumping PR
for gcc-cross would just give people a false sense of security. I'm not
against bumping PR for gcc-cross, I'm just saying that it doesn't come
close to fixing the problem at hand, which is packages with missing
dependencies (libgcc for normal ones, libstdc++ for c++ ones,
libgfortran for fortran ones, etc).

> Thinking of it let's see how many distro's actually use DISTRO_PR:
> ../../conf/distro/angstrom-2008.1.conf:DISTRO_PR = ".6"
> ../../conf/distro/kaeilos-2010.conf:DISTRO_PR = ".1"
> ../../conf/distro/kaeilos.conf:DISTRO_PR = ".5"
> ../../conf/distro/angstrom-2010.x.conf:DISTRO_PR = ".7"
> ../../conf/distro/shr.conf:DISTRO_PR = ".5"
> 
> So that is 5 out of the 32 recipes.
> Even one of your own (angstrom-2008.1-legacy.conf) does ot use DISTRO_PR

Do you know how requires work in OE?

conf/distro$ grep require angstrom-2008.1-legacy.conf
require conf/distro/angstrom-2008.1.conf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMjL3+MkyGM64RGpERAsRvAJ43TZNi07Md1wcPxdz5T6KaYYl8AwCgvNLY
X+Hd1AJVQULZ0BDAiiU6X5A=
=hIhF
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-09-12 11:49 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
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 [this message]
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='i6ielv$sld$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox