public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: cgd@broadcom.com, binutils@sources.redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: problems re: makeinfo '--split-size' arg?
Date: Tue, 29 Apr 2003 14:13:00 -0000	[thread overview]
Message-ID: <1051625559.7385.3.camel@steven> (raw)
In-Reply-To: <Pine.BSF.4.53.0304291416050.44098@naos.dbai.tuwien.ac.at>

Op di 29-04-2003, om 16:06 schreef Gerald Pfeifer:
> 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

I suppose the comment should be changed here, then?  We don't set a
threshold, so the comment doesn't make sense anymore.

> 
>  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

Same here.

> 
>  EXPECT = `if [ -f $$r/expect/expect ] ; \
>  	then echo $$r/expect/expect ; \
> 


Greetz
Steven


  reply	other threads:[~2003-04-29 14:13 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 ` problems re: makeinfo '--split-size' arg? Gerald Pfeifer
2003-04-29 14:13   ` Steven Bosscher [this message]
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=1051625559.7385.3.camel@steven \
    --to=s.bosscher@student.tudelft.nl \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).