public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/4096: libstdc++-v3/include/Makefile.in has several errors in it
Date: Thu, 23 Aug 2001 14:56:00 -0000	[thread overview]
Message-ID: <20010823215600.9715.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR libstdc++/4096; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: rkl@connect.org.uk
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/4096: libstdc++-v3/include/Makefile.in has several errors in it
Date: Thu, 23 Aug 2001 16:29:47 -0400

 On Thu, Aug 23, 2001 at 02:40:48PM -0000, rkl@connect.org.uk wrote:
 > >Environment:
 > HP-UX 11.00, but probably applies to most platforms
 
 Nope.
 
 > >Description:
 > The new Makefile.in added with 3.0.1, namely
 > libstdc++-v3/include/Makefile.in has several problems:
 > 
 > * The lengths of lines are excessive - HP-UX 11.00's vi
 >   can't edit them.
 
 The very first line of Makefile.in tells you that the file is automatically
 generated.  You're not supposed to be editing them directly.  (Users who
 do are assumed to have a decent text editor like vim.)
 
 > * The path for the rules involving gthr.h, gthr-single.h
 >   and gthr-default.h seem to be one level too low, causing
 >   the build to bomb out.
 
 That is a bug, already reported.  I think it might already be fixed in
 the development tree.
 
 > * Use of "-d" with the $(INSTALL) command isn't
 >   cross-platform (many install scripts don't support it) -
 >   see the install-data-local rule.
 
 Have you seen what $(INSTALL) evaluates to?  GCC ships its own installation
 script.
 
 
 > * "make install" installs the Makefile.in, Makefile and
 >   Makefile.am files into the install tree of gcc !!!!!
 
 Already fixed in the 3.1 tree.  The patch that did it hasn't yet been
 applied to the 3.0.x tree, but probably will be soon.  (It's a harmless
 but amusing bug.)
 
 
 Phil
 
 -- 
 Would I had phrases that are not known, utterances that are strange, in
 new language that has not been used, free from repetition, not an utterance
 which has grown stale, which men of old have spoken.
                                      - anonymous Egyptian scribe, c.1700 BC


             reply	other threads:[~2001-08-23 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 14:56 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-28 15:18 pme
2001-08-23  7:46 rkl

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=20010823215600.9715.qmail@sourceware.cygnus.com \
    --to=pedwards@disaster.jaj.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).