public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Hollstein <manfred@s-direktnet.de>
To: law@cygnus.com
Cc: wilson@cygnus.com, egcs@cygnus.com
Subject: Re: New texinfo still breaks `make bootstrap`
Date: Mon, 06 Apr 1998 02:35:00 -0000	[thread overview]
Message-ID: <13608.30812.973943.633396@slsvhmt> (raw)
In-Reply-To: <15798.891582845@hurl.cygnus.com>

On Thu, 2 April 1998, 22:54:05, law@cygnus.com wrote:

 > 
 >   In message < 199803310231.SAA11043@rtl.cygnus.com >you write:
 >   > A lot texinfo related problems could be fixed simply by not building the
 >   > stuff we don't need.  For instance, this gets me past the texinfo build
 >   > problems others are reporting, though I don't know yet whether the resulting
 >   > makeinfo program works, my build is still going.
 >   > 
 >   > There was a similar change in the old EGCS texinfo sources.
 >   > 	Fri Oct 31 09:39:31 1997  Jeffrey A Law  (law@cygnus.com)
 >   > 	* Makefile.in (install targets): Add a dummy target for sunos make.
 >   > 	(SUBDIR): Remove 'info'.  It's unneeded.
 > Part of the original idea behind not building certain things was
 > because our texinfo was horribly out of date and we didn't want to
 > build anything except the bare bones necessary to format the docs.
 > Similarly we tweaked make install to do nothing to avoid overwriting
 > a previously installed texinfo (which would probably have been newer
 > than the one egcs would install).
 > 
 > So the question at had is do we want to continue the the practice
 > of not building stuff we don't need and not installing texinfo?

Last Saturday I did a `make install' and got pretty surprised when I
saw, it did not only install the usual `gcc', `c++', `g++' ... but
`info', `makeinfo', `texi2dvi', ... and even the texinfo related
locale files. Unnecessary to say, it completely overwrote my previous
texinfo-3.12 installation :-)

 > 
 > I don't care much either way.

I'd prefer not to build and/or install anything which doesn't actually 
belong to egcs.

 > 
 > jeff

manfred

      reply	other threads:[~1998-04-06  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.3.96.980328115215.14742A-100000@markab.dbai.tuwien.ac.at>
1998-03-31  0:46 ` Jim Wilson
1998-04-04 11:01   ` Jeffrey A Law
1998-04-06  2:35     ` Manfred Hollstein [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13608.30812.973943.633396@slsvhmt \
    --to=manfred@s-direktnet.de \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=wilson@cygnus.com \
    /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).