From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rolf Leggewie <no2spam@nospam.arcornews.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC after the fact - bug 1987
Date: Fri, 16 Mar 2007 19:00:01 +0200 [thread overview]
Message-ID: <862875582.20070316190001@gmail.com> (raw)
In-Reply-To: <etecci$200$1@sea.gmane.org>
Hello Rolf,
Friday, March 16, 2007, 6:16:34 PM, you wrote:
> Hi,
> it seems I have still a few things to learn as far as updating OE
> metadata goes. Furthermore it seems I might have created the first
> major fuck-up. I apologize for the inconvenience this has caused to the
> OE community.
> Now, to sort things out; I committed
> a96c9acac99b5599d2b0fb0a518603646414d166 yesterday to fix bug 1987. It
> seemed like an obvious case (move debug files into -dbg package) which
> is why I dared to commit. psokolovsky made me aware that an RFC had
> been necessary to make this commit to a core part of OE and that it
> might have broken compilation for some OE users.
> Now here I am trying to do The Right Thing[TM]. I want to discuss "mtn
> diff -r e9d53f524190d295cb769c7594711fd76eb197b7 -r
> a96c9acac99b5599d2b0fb0a518603646414d166". Please let me know if there
> is anything wrong with this change. If it should be reverted, feel free
> to do so or let me know via mail or IRC and I will fix it pronto.
I doubt that it's due to that easy change. I suspect your earlier
commits, 2c516898480b1bc053c9cbf6da853a016059c4c6 &
286930242424d10b2503eb290dbc31c7975bab74 are to blame.
Either way, I get here:
$bitbake angstrom-x11-image
OE Build Configuration:
BB_VERSION = "1.6.7"
OE_REVISION = "25edfc91e04a9233cb67583981d1d8aa3e82f0c0"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "h4000"
DISTRO = "angstrom"
DISTRO_VERSION = "test-20070316"
TARGET_FPU = "soft"
NOTE: preferred version 2.5 of glibc not available
NOTE: preferred version 2.6.19-hh8 of linux-handhelds-2.6 not available
NOTE: preferred version 2.6.19-hh8 of linux-handhelds-2.6 not available
NOTE: preferred version 2.5 of glibc-initial not available
NOTE: preferred version 2.5 of glibc not available
NOTE: preferred version 2.5 of glibc-intermediate not available
NOTE: multiple preferred providers are available (glibc, glibc, glibc);
NOTE: consider defining only one PREFERRED_PROVIDER to match runtime glibc-gconv-iso8859-1
NOTE: package glibc-2.3.5+cvs20050627: started
Whereas:
bitbake glibc -v
NOTE: Selecting already-staged glibc (2.5-r5) to satisfy glibc
(-c rebuild rebuilds 2.5)
The same was report by at least 3 other people, including using
other distro than Angstrom.
> Regards
> Rolf
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-03-16 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 16:16 RFC after the fact - bug 1987 Rolf Leggewie
2007-03-16 17:00 ` Paul Sokolovsky [this message]
2007-03-16 18:43 ` Rolf Leggewie
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=862875582.20070316190001@gmail.com \
--to=pmiscml@gmail.com \
--cc=no2spam@nospam.arcornews.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