From: Andreas Schwab <schwab@linux-m68k.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change to bzr build instructions
Date: Tue, 22 Mar 2011 10:32:06 +0100 [thread overview]
Message-ID: <m362rbqz55.fsf@linux-m68k.org> (raw)
In-Reply-To: <30r5a1s4kt.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 20 Mar 2011 20:24:50 -0400")
Glenn Morris <rgm@gnu.org> writes:
> The autotools generated files such as configure are no longer present in
> the repository in the trunk. Instead you should generate them yourself
> using the autogen.sh script. See INSTALL.BZR for details.
You should also remove all the other files that would be added by
running autoreconf (config.{guess,sub}, depcomp, missing, etc.).
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."
next prev parent reply other threads:[~2011-03-22 9:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 0:24 Change to bzr build instructions Glenn Morris
2011-03-21 0:46 ` Glenn Morris
2011-03-21 16:06 ` Jim Meyering
2011-03-21 22:33 ` Stefan Monnier
2011-03-22 3:31 ` Glenn Morris
2011-03-22 5:42 ` Stefan Monnier
2011-03-22 7:16 ` Glenn Morris
2011-03-22 8:08 ` Jim Meyering
2011-03-22 9:32 ` Andreas Schwab [this message]
2011-03-23 3:15 ` Glenn Morris
2011-03-22 11:36 ` Andreas Röhler
2011-03-22 13:09 ` Harald Hanche-Olsen
2011-03-22 18:37 ` Glenn Morris
2011-03-25 9:54 ` Eli Zaretskii
2011-03-25 10:04 ` David Kastrup
2011-03-25 10:18 ` Eli Zaretskii
2011-03-25 11:44 ` Leo
2011-03-25 13:07 ` David Kastrup
2011-03-25 13:13 ` Eli Zaretskii
2011-03-25 13:52 ` David Kastrup
2011-03-25 16:02 ` Eli Zaretskii
2011-03-25 13:45 ` Andreas Röhler
2011-03-27 18:54 ` Davis Herring
2011-03-25 14:37 ` Ted Zlatanov
2011-03-25 15:03 ` David Kastrup
2011-03-25 15:16 ` Ted Zlatanov
2011-03-25 15:32 ` David Kastrup
2011-03-25 16:08 ` Eli Zaretskii
2011-03-25 19:55 ` Stefan Monnier
2011-03-28 1:11 ` Miles Bader
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=m362rbqz55.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).