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++/4071: "make install" installs .../include/g++-v3/Makefile Date: Wed, 22 Aug 2001 15:56:00 -0000 [thread overview] Message-ID: <20010822225601.7508.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/4071; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: libstdc++/4071: "make install" installs .../include/g++-v3/Makefile Date: Wed, 22 Aug 2001 17:25:38 -0400 On Wed, Aug 22, 2001 at 01:06:00AM -0000, Phil Edwards wrote: > That's... amusing. Happening here too, although not on the 3.1 branch. > A quick look at the differences between the branches doesn't point out > anything obvious to me, but it was just a quick look. Obviously I'm blind. A simple annotation search points to this on mainline: 2001-08-07 Benjamin Kosnik <bkoz@redhat.com> Implement std::messages. [...] * include/Makefile.am (install-data-local): Don't install Makefile. So this will be fixed whenever this patch goes over into the branch. Since it isn't a critical issue, there's no point in making the future merging any more difficult than it usually is by moving pieces of the patch early. In the meantime we'll just have to hope that nobody chdir's into the header installation directory and types 'make'. :-) 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
next reply other threads:[~2001-08-22 15:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-22 15:56 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-10-10 13:40 pme 2001-08-24 17:15 bkoz 2001-08-21 18:06 Phil Edwards 2001-08-21 10:16 Phil Richards
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=20010822225601.7508.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: linkBe 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).