From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: cgd@broadcom.com
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: problems re: makeinfo '--split-size' arg?
Date: Tue, 29 Apr 2003 14:06:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.53.0304291416050.44098@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <yov5k7dev7e3.fsf@broadcom.com>
On Mon, 28 Apr 2003 cgd@broadcom.com wrote:
>> makeinfo (GNU texinfo) 4.0
As Joseph (who is the expert on that) wrote we actually require makeinfo
4.2 for GCC and I agree that it should we checked automatically, as per
your patch.
Still, what I can do, and have in fact considered for the 3.3 branch also
before, is using --no-split instead of --split-size, as it shouldn't make
a difference there (except, in fact working around a "feature" of
--split-size in currently released versions of texinfo).
Bootstrapped and installed the 3.3-branch on i386-unknown-freebsd4.8,
committed to the 3.3-branch.
Gerald
2003-04-29 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* Makefile.tpl (MAKEINFOFLAGS): Use --no-split instead of
--split-size.
* Makefile.in: Regenerate.
Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/Makefile.in,v
retrieving revision 1.129.2.5
diff -u -3 -p -r1.129.2.5 Makefile.in
--- Makefile.in 25 Apr 2003 20:27:39 -0000 1.129.2.5
+++ Makefile.in 29 Apr 2003 14:04:18 -0000
@@ -163,7 +163,7 @@ MAKEINFO = `if [ -f $$r/texinfo/makeinfo
# sub-makes. It lets flags be given on the command line while still
# using the makeinfo from the object tree.
# (Default to avoid splitting info files by setting the threshold high.)
-MAKEINFOFLAGS = --split-size=5000000
+MAKEINFOFLAGS = --no-split
EXPECT = `if [ -f $$r/expect/expect ] ; \
then echo $$r/expect/expect ; \
Index: Makefile.tpl
===================================================================
RCS file: /cvs/gcc/gcc/Makefile.tpl,v
retrieving revision 1.13.6.4
diff -u -3 -p -r1.13.6.4 Makefile.tpl
--- Makefile.tpl 25 Apr 2003 20:27:39 -0000 1.13.6.4
+++ Makefile.tpl 29 Apr 2003 14:04:19 -0000
@@ -166,7 +166,7 @@ MAKEINFO = `if [ -f $$r/texinfo/makeinfo
# sub-makes. It lets flags be given on the command line while still
# using the makeinfo from the object tree.
# (Default to avoid splitting info files by setting the threshold high.)
-MAKEINFOFLAGS = --split-size=5000000
+MAKEINFOFLAGS = --no-split
EXPECT = `if [ -f $$r/expect/expect ] ; \
then echo $$r/expect/expect ; \
next prev parent reply other threads:[~2003-04-29 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 17:50 cgd
2003-04-28 18:55 ` Joseph S. Myers
[not found] ` <mailpost.1051556216.2781@news-sj1-1>
2003-05-01 17:27 ` cgd
2003-05-02 6:23 ` Gerald Pfeifer
2003-05-02 21:44 ` [patch] cgd
2003-05-02 21:45 ` [patch] require makeinfo 4.2 or better cgd
2003-04-29 14:06 ` Gerald Pfeifer [this message]
2003-04-29 14:13 ` problems re: makeinfo '--split-size' arg? Steven Bosscher
2003-04-29 15:04 ` Gerald Pfeifer
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=Pine.BSF.4.53.0304291416050.44098@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.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.
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).