From: Glenn Morris <rgm@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Nick Roberts <nickrob@snap.net.nz>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Emacs can't be built without recent makeinfo
Date: Fri, 25 Apr 2008 14:48:48 -0400 [thread overview]
Message-ID: <j0abjhvkhb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 18450.1350.18815.221139@a1ihome1.kph.uni-mainz.de
Ulrich Mueller wrote:
>>> Do we really want to stop the build process completely just
>>> because the online manuals can't be properly built?
The "online manuals" are a vital part of Emacs, so yes...
>> Indeed, no. Especially since they are supposed to be pre-built in
>> the tarball.
...however in many cases they are pre-built.
>> The test should/could be moved to the Makefile, maybe?
>
> Is this really an issue? texinfo 4.6 was released in 2003.
I agree with you. Perhaps the issue is the need to have _any_ version
of texinfo though.
The info files are already only deleted by `make maintainer-clean',
which "may require special tools to rebuild", so that's fine.
We don't check for autoconf etc either.
One problem I see is that the info files aren't in the CVS, so a fresh
checkout could fail to build. And also any update to the .texi files
will trigger a rebuild. So basically there are only problems with CVS
builds.
Perhaps a check early on in the Makefile will suffice, but it seems
a bit flaky?
next prev parent reply other threads:[~2008-04-25 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 4:45 Emacs can't be built without recent makeinfo Nick Roberts
2008-04-25 13:45 ` Stefan Monnier
2008-04-25 16:22 ` Ulrich Mueller
2008-04-25 18:48 ` Glenn Morris [this message]
2008-04-25 22:06 ` Nick Roberts
2008-04-25 23:26 ` Glenn Morris
2008-05-03 20:17 ` Glenn Morris
2008-05-03 21:07 ` Jason Rumney
2008-05-03 21:12 ` Glenn Morris
2008-05-03 21:38 ` Jason Rumney
2008-05-04 1:58 ` Glenn Morris
2008-05-04 3:55 ` Eli Zaretskii
2008-05-05 18:31 ` Glenn Morris
2008-05-04 21:15 ` Nick Roberts
2008-04-25 22:47 ` Magnus Henoch
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=j0abjhvkhb.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
--cc=ulm@gentoo.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).