From: Andreas Schwab <schwab@suse.de>
Cc: emacs-devel@gnu.org
Subject: Re: Changing configure.in and make-tarball.txt
Date: Sat, 13 Sep 2003 17:12:24 +0200 [thread overview]
Message-ID: <jehe3gu3hj.fsf@sykes.suse.de> (raw)
In-Reply-To: <m3smn1fvzc.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "13 Sep 2003 01:05:59 +0200")
no-spam@cua.dk (Kim F. Storm) writes:
> I suppose (read: guess) the proper steps are:
>
> edit configure.in
> rm -f configure src/config.in config.status
> autoconf
> autoheader
That shouldn't be needed if you configure with --enable-maintainer-mode.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2003-09-13 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 23:05 Changing configure.in and make-tarball.txt Kim F. Storm
2003-09-13 15:12 ` Andreas Schwab [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
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=jehe3gu3hj.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@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 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).