From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] State of bitbake world, Failed tasks 2014-06-02
Date: Fri, 20 Jun 2014 12:24:01 +0200 [thread overview]
Message-ID: <lo1242$195$1@ger.gmane.org> (raw)
In-Reply-To: <1403258272.2104.87.camel@ted>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef op 20-06-14 11:57:
> I know that with some of the changes in oe-core, meta-oe is suffering a
> little. I've been working on fixing up some of a world build of meta-oe
> with patches including the problematic autoconf one applied.
>
> My WIP is:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=rpurdie/meta-oe&id=9ece5e493b7844a7282eb883effa9d9a5b56d20e
Thanks!
>
>
I appreciate its a huge patch and needs splitting up but there are only
> so many hours in the day.
>
> Of note are a few sepbuild fixes in there and one for the binconfig pcre
> issue that apache2 has, introduced by the binconfig change in OE-Core. I
> took the opportunity to clean up the -native recipe a bit, it should be
> closer to the main recipe and allow it to be converted to BBCLASSEXTEND
> in due course.
Looks like we did similar things: http://patches.openembedded.org/patch/73919/
I noticed that the LAMP recipes are really, really ugly for historical
reasons. With the autotools updates in oe-core and a few years of upstream
development most hacks aren't needed anymore. Any volunteers for cleaning up
those recipes?
regards,
Koen
>
> There are some fixes for talloc which I know has caused some headaches
> too.
>
> I will try and find the time to clean this up and submit it piece by
> piece but if anyone beats me to it, great and hopefully nobody will
> duplicate the work.
>
> Cheers,
>
> Richard
>
>
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFTpAvBMkyGM64RGpERApouAKCavK3jHaxDCXx8XVGAgoYniV5GFwCfSw7C
DmtUiAcJng1kxC/EBMWaY+k=
=o518
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-06-20 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 10:07 State of bitbake world, Failed tasks 2014-06-02 Martin Jansa
2014-06-10 11:40 ` Martin Jansa
2014-06-12 11:06 ` Richard Purdie
2014-06-10 15:40 ` akuster@mvista
2014-06-20 9:57 ` [oe] " Richard Purdie
2014-06-20 10:24 ` Koen Kooi [this message]
2014-06-21 9:04 ` Paul Eggleton
2014-06-21 8:51 ` Martin Jansa
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='lo1242$195$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--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