From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix build failure of openjade using newer host
Date: Tue, 12 Jun 2012 14:13:40 +0100 [thread overview]
Message-ID: <1339506820.8065.2.camel@ted> (raw)
In-Reply-To: <CAP9ODKo415ewPTCpy5_dmziRRZgqesjof6zBKmjgHgDFO_XrcA@mail.gmail.com>
On Fri, 2012-06-08 at 08:52 -0300, Otavio Salvador wrote:
> On Fri, Jun 8, 2012 at 7:33 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> Why can't we run autoreconf instead of having the huge patch?
> This might
> be the right answer but I'd like to understand the problem
> here a bit
> more...
>
> The configure scripts are inside config dir and to proper configure it
> you need to call it with some params; too hackish! I ended getting
> this change from Debian package to not waste time mangling with
> options for autoreconf and like.
I really want to run reautoconf like we do with the rest of the system
for consistency. Its less important as long as this is a native recipe
but if we started building it for the target it would become a problem.
I appreciate you don't want to get distracted with something like that
and I can't really ask you to do it so I've done it myself put out an
alternative patch for review.
Cheers,
Richard
next prev parent reply other threads:[~2012-06-12 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 17:34 [PATCH 0/1] Fix build failure of openjade using newer host Otavio Salvador
2012-06-02 17:34 ` [PATCH 1/1] openjade: autoreconf to fix building on newer host systems Otavio Salvador
2012-06-11 17:34 ` Flanagan, Elizabeth
2012-06-12 0:23 ` Scott Garman
2012-06-12 13:14 ` Richard Purdie
2012-06-08 10:33 ` [PATCH 0/1] Fix build failure of openjade using newer host Richard Purdie
2012-06-08 11:52 ` Otavio Salvador
2012-06-12 13:13 ` Richard Purdie [this message]
2012-06-12 13:16 ` Otavio Salvador
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=1339506820.8065.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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