From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problem in bitbaking
Date: Thu, 04 Feb 2010 14:03:22 +0100 [thread overview]
Message-ID: <4B6AC59A.90000@dresearch.de> (raw)
In-Reply-To: <20100203162120.GB26844@xora-build.xora.org.uk>
Graeme Gregory wrote:
>>> Since today i see a similar problem when doing a clean bitbake of
>>> glib-2.0. It seems to be a problem with automake/automake. :(
>>
>> I think i've identified this patch as cause of the problems.
>>
>> commit b1caa21ab2590689f3b6ff68483803701c12d721
>> Author: Graeme Gregory <dp@xora.org.uk>
>> Date: Tue Jan 26 12:02:08 2010 +0000
>>
> Guys there is zero point sending me emails direct if you dont actually
> tell me any information.
Sorry about that. But i wasn't sure if you read the ml daily. So i put
you on the Cc.
BTW, i would call the hint, that your commit broke[1] the baking of at
least glib-2.0 (which isn't that exotic) an 'information'.
[1] I've rechecked this again with angstrom distro and hipox,
beagleboard, and x86 machine making a clean build of glib-2.0:
rm -rf tmp.5
bitbake glib-2.0
Steffen
next prev parent reply other threads:[~2010-02-04 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 15:14 Problem in bitbaking saleh usman
2010-02-02 16:06 ` Steffen Sledz
2010-02-03 15:55 ` Steffen Sledz
2010-02-03 16:21 ` Graeme Gregory
2010-02-04 13:03 ` Steffen Sledz [this message]
2010-02-04 13:10 ` Philip Balister
2010-02-04 13:22 ` Graeme Gregory
2010-02-04 13:59 ` Steffen Sledz
2010-02-07 16:09 ` Graeme Gregory
2010-02-08 7:37 ` Steffen Sledz
2010-02-04 13:49 ` Frans Meulenbroeks
2010-02-04 14:15 ` Steffen Sledz
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 14:49 problem " saleh usman
2010-02-03 15:21 ` Frans Meulenbroeks
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=4B6AC59A.90000@dresearch.de \
--to=sledz@dresearch.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