all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Thien-Thi Nguyen <ttn@gnu.org>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>,
	Hongxu Chen <leftcopy.chx@gmail.com>
Subject: Re: What should I do when building Emacs again with different configure options?
Date: Mon, 29 Jul 2013 06:56:15 +0800	[thread overview]
Message-ID: <CAAF+z6HENSocHHf68vC9yu5VSERUWGyEYKSJmVW533yVgJTXQg@mail.gmail.com> (raw)
In-Reply-To: <F171FADE-D12D-476B-9E43-3B3716890624@Web.DE>

On Sun, Jul 28, 2013 at 11:44 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
>
> Am 28.07.2013 um 15:33 schrieb Xue Fuqiao:
>
>> It already implies that we _need_ different configure option(s), so we
>> don't need the second extra line.  What's your opinion?
>
> The second mentioning of "./configure" should be extended to
>
>         ./configure <your choice of options and settings>
>
> With "options" I mean the --<things>, with "settings" I mean the
> "influential environment variables".

Sounds fine to me.  Glenn?

-- 
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/



  reply	other threads:[~2013-07-28 22:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27  1:59 What should I do when building Emacs again with different configure options? Xue Fuqiao
2013-07-27  2:06 ` Glenn Morris
2013-07-27 22:30   ` Xue Fuqiao
2013-07-27 22:53     ` Peter Dyballa
2013-07-28 13:38       ` Xue Fuqiao
2013-07-28  2:03     ` Hongxu Chen
2013-07-28  8:39       ` Thien-Thi Nguyen
2013-07-28 13:33         ` Xue Fuqiao
2013-07-28 15:19           ` Thien-Thi Nguyen
2013-07-28 15:44           ` Peter Dyballa
2013-07-28 22:56             ` Xue Fuqiao [this message]
2013-07-28 23:47               ` Glenn Morris
2013-07-29  1:32                 ` Xue Fuqiao
2013-07-28 13:50       ` Xue Fuqiao
2013-07-27  9:17 ` Peter Dyballa

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=CAAF+z6HENSocHHf68vC9yu5VSERUWGyEYKSJmVW533yVgJTXQg@mail.gmail.com \
    --to=xfq.free@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=leftcopy.chx@gmail.com \
    --cc=rgm@gnu.org \
    --cc=ttn@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.