From: Constantin Musca <constantinx.musca@intel.com>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] automake 1.12.3: fix warnings
Date: Mon, 10 Sep 2012 15:39:06 +0300 [thread overview]
Message-ID: <504DDF6A.1020409@intel.com> (raw)
In-Reply-To: <1347283193.2673.240.camel@phil-desktop>
On 09/10/2012 04:19 PM, Phil Blundell wrote:
> On Thu, 2012-09-06 at 12:49 +0300, Constantin Musca wrote:
>> +++ b/meta/recipes-devtools/automake/automake/no-configure.in-warn.patch
>> @@ -0,0 +1,19 @@
>> +Don't show a warning if configure.in exists
>> +
>> +Upstream-Status: Inappropriate [embedded specific]
>> +
>> +Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
>> +
>> +--- a/lib/Automake/Configure_ac.pm
>> ++++ b/lib/Automake/Configure_ac.pm
>> +@@ -77,8 +77,8 @@ sub find_configure_ac (;@)
>> +
>> + if (-f $configure_in)
>> + {
>> +- msg ('obsolete', "autoconf input should be named 'configure.ac'," .
>> +- " not 'configure.in'");
>> ++# msg ('obsolete', "autoconf input should be named 'configure.ac'," .
>> ++# " not 'configure.in'");
> Why is this change "embedded specific"?
>
> p.
>
>
Good question :). The Upstream-Status has to be Inappropriate [
configuration ]. Anyway, this patch will not be merged because we
decided that we have to patch the packages instead to eliminate the warning.
Cheers,
Constantin Musca
prev parent reply other threads:[~2012-09-10 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 9:49 [PATCH] automake 1.12.3: fix warnings Constantin Musca
2012-09-06 18:49 ` Saul Wold
2012-09-07 8:32 ` Constantin Musca
2012-09-10 13:19 ` Phil Blundell
2012-09-10 12:39 ` Constantin Musca [this message]
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=504DDF6A.1020409@intel.com \
--to=constantinx.musca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.