From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [oe] [PATCH 0/7][RFC] Remove enforced --foreign in autoreconf
Date: Wed, 16 Jul 2014 23:47:01 +0100 [thread overview]
Message-ID: <1405550821.3668.9.camel@ted> (raw)
In-Reply-To: <20140715165842.GN2433@jama>
On Tue, 2014-07-15 at 18:58 +0200, Martin Jansa wrote:
> On Tue, Jul 15, 2014 at 05:18:30PM +0100, Ross Burton wrote:
> > Hi,
> >
> > Since 2004 we've been forcibly passing --foreign to automake in autoreconf.
> > This is a change from upstream behaviour and can actually break packages that
> > expect GNU behaviour (admittedly the failure case reported was "interesting"),
> > and I'm on a bit of a mission to remove patches that don't have a solid reason
> > behind them.
> >
> > Forcing --foreign doesn't seem that important these days as the majority of
> > packages are telling automake they're foreign, There are a few packages that
> > need patches for this change, notably they're mostly packages that haven't seen
> > a release for ten years.
> >
> > This series is build tested against a world build in oe-core for NUC, so I'd
> > call it a demonstration that the patch is viable and would appreciate others
> > running build tests against other machines or layers.
>
> world builds from
> http://www.openembedded.org/wiki/Bitbake_World_Status
> already have around ~50 failed recipes per architecture, I don't think
> we need more now :/
>
> Do we have some volunteers to fix-up meta-oe/* layers?
>
> I'm going to use PNBLACKLIST more aggressively as agreed on OEDAM, but
> with this speed next meta-oe release will have half of recipes which
> were available in daisy.
I made a quick test and the failures I spotted from meta-oe likely due
to this patch were:
re2c
libsdl-iomage
claws-plugin-gtkhtml2-viewer
claws-plugin-rssyl
libsdl-tiff
libol
ode
dejagnu
memcached
rp-pppoe
ipsec-tools
mtr
hplip
onig
Its probably not a complete list as I have a lot more failures than your
world builds but it gives some idea of number and its not a massive
list.
Cheers,
Richard
next prev parent reply other threads:[~2014-07-16 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 16:18 [PATCH 0/7][RFC] Remove enforced --foreign in autoreconf Ross Burton
2014-07-15 16:18 ` [PATCH 1/7] bzip2: use "foreign" automake strictness Ross Burton
2014-07-15 16:18 ` [PATCH 2/7] libid3tag: " Ross Burton
2014-07-15 16:18 ` [PATCH 3/7] which: " Ross Burton
2014-07-15 16:18 ` [PATCH 4/7] libmad: " Ross Burton
2014-07-15 16:18 ` [PATCH 5/7] oprofile: " Ross Burton
2014-07-15 16:18 ` [PATCH 6/7] ltp: " Ross Burton
2014-07-15 16:18 ` [PATCH 7/7] autoconf: remove automake patch enforcing --foreign Ross Burton
2014-07-15 20:14 ` [oe] " Khem Raj
2014-07-15 21:51 ` Burton, Ross
2014-07-16 16:39 ` Khem Raj
2014-07-15 16:58 ` [oe] [PATCH 0/7][RFC] Remove enforced --foreign in autoreconf Martin Jansa
2014-07-16 22:47 ` Richard Purdie [this message]
2014-07-17 22:11 ` Richard Purdie
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=1405550821.3668.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--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