From: Pete Williamson <petewil@google.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Michal Nazarewicz <mina86@mina86.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] - Introduce reference to a new Emacs build target - NaCl
Date: Wed, 18 Mar 2015 09:04:13 -0700 [thread overview]
Message-ID: <CAHsSLHBSJ2j-8P_==1N3uK9kPdrYymyqeLrsqafg9oPz+vrNJg@mail.gmail.com> (raw)
In-Reply-To: <CAHsSLHA-qpbE_f78Uu3sNhW6pzEztqnVF67zQAfALK2-SDQN6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
Since there has been no other feedback on this topic, I'll take Michal's
suggestion (and clear up Paul's confusion), and make all the changes to the
config.ac file at once, stay tuned for an updated patch.
On Fri, Mar 13, 2015 at 5:29 PM, Pete Williamson <petewil@google.com> wrote:
> The actual patch is to configure.ac. The diff is showing things that I
> would move from my current "configure" file to "configure.ac"
>
> On Fri, Mar 13, 2015 at 5:28 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
>> Pete Williamson wrote:
>>
>>> --- a/configure
>>> +++ b/configure
>>>
>>
>> 'configure' is generated automatically from 'configure.ac' and other
>> files, so patches to 'configure' are ineffective. You need to patch
>> configure.ac and the other files instead.
>>
>> If you need to patch config.guess and/or config.sub, they come from a
>> different project and those changes need to be sent upstream, as described
>> in those files.
>>
>
>
[-- Attachment #2: Type: text/html, Size: 1969 bytes --]
next prev parent reply other threads:[~2015-03-18 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 21:57 [PATCH] - Introduce reference to a new Emacs build target - NaCl Pete Williamson
2015-03-13 23:44 ` Michal Nazarewicz
2015-03-13 23:46 ` Pete Williamson
2015-03-14 0:28 ` Paul Eggert
2015-03-14 0:29 ` Pete Williamson
2015-03-18 16:04 ` Pete Williamson [this message]
2015-03-28 0:30 ` Pete Williamson
2015-03-29 21:50 ` Paul Eggert
2015-03-30 10:12 ` Richard Stallman
2015-03-30 21:41 ` Pete Williamson
2015-03-31 14:06 ` Richard Stallman
2015-03-31 18:29 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHsSLHBSJ2j-8P_==1N3uK9kPdrYymyqeLrsqafg9oPz+vrNJg@mail.gmail.com' \
--to=petewil@google.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=mina86@mina86.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).