all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MAKEINFO variable not honoured
Date: Mon, 03 Jan 2011 09:50:59 +0100	[thread overview]
Message-ID: <m2hbdq1ibw.fsf@whitebox.home> (raw)
In-Reply-To: <20110103.093611.376233976.wl@gnu.org> (Werner LEMBERG's message of "Mon, 03 Jan 2011 09:36:11 +0100 (CET)")

Werner LEMBERG <wl@gnu.org> writes:

>>> -MAKEINFO = makeinfo --force -I $(emacsdir) -I $(srcdir)
>>> +MAKEINFO = @MAKEINFO@ --force -I $(emacsdir) -I $(srcdir)
>> 
>> The line should read "MAKEINFO = @MAKEINFO@" exactly, with the extra
>> options being put in a different variable.
>
> Originally, I've done this, and I can change this easily.  Is there a
> rationale behind this limitation?

It's not a limitation.  It makes it possible to properly override it
without reconfiguring.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2011-01-03  8:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-01 12:21 MAKEINFO variable not honoured Werner LEMBERG
2011-01-03  5:23 ` Werner LEMBERG
2011-01-03  5:50   ` Glenn Morris
2011-01-03  6:20     ` Werner LEMBERG
2011-01-03  8:22 ` Andreas Schwab
2011-01-03  8:36   ` Werner LEMBERG
2011-01-03  8:50     ` Andreas Schwab [this message]
2011-01-03 18:23       ` Werner LEMBERG
2011-01-21 18:36         ` Werner LEMBERG
2011-01-22 16:00           ` Chong Yidong
2011-01-23 10:39             ` Werner LEMBERG
2011-01-23 11:45               ` Eli Zaretskii
2011-01-23 11:57                 ` Werner LEMBERG
2011-01-23 12:41                   ` Eli Zaretskii
2011-01-23 14:11                     ` Werner LEMBERG

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=m2hbdq1ibw.fsf@whitebox.home \
    --to=schwab@linux-m68k.org \
    --cc=emacs-devel@gnu.org \
    --cc=wl@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.