public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5095: broken $(MAKEFLAGS)
Date: Thu, 18 Apr 2002 22:26:00 -0000	[thread overview]
Message-ID: <20020419052604.836.qmail@sources.redhat.com> (raw)

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

From: Phil Edwards <phil@jaj.com>
To: "Golubev I. N." <gin@mo.msk.ru>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: libstdc++/5095: broken $(MAKEFLAGS)
Date: Fri, 19 Apr 2002 01:17:23 -0400

 On Sun, Apr 14, 2002 at 03:41:28PM +0000, Golubev I. N. wrote:
 > On Thu, 13 Dec 2001 18:32:00 (GMT) I wrote to gcc-bugs@gcc.gnu.org in
 > <01e43c18f42036-gin@mo.msk.ru>:
 > 
 > > My apologies.  That happens only if
 > > 
 > > MAKEOVERRIDES = 
 > > 
 > > line is removed from `libstdc++-v3/Makefile', which does not normally
 > > happen with gcc.
 > 
 > It should be displayed in list archive as a followup to original
 > report, but it looks like it is not.  How do I ensure that in future?
 
 Make certain that gcc-gnats is in the To:/Cc: header, and that the PR
 number (libstdc++/5095) is in the Subject: header.  Then it will be
 appended automatically.
 
 
 > The real problem is that "trying to override a makefile variable gets
 > tricky when recursing".  Current gcc configuration scripts constantly
 > lack something essential for one's favorite system, and overriding
 > makefile variables is often required.  Documenting ways to do it is
 > absolutely necessary.
 
 Unfortunately no two libraries are the same.  Patches welcome.
 
 
 -- 
 If ye love wealth greater than liberty, the tranquility of servitude greater
 than the animating contest for freedom, go home and leave us in peace.  We seek
 not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
 and may posterity forget that ye were our countrymen.            - Samuel Adams


             reply	other threads:[~2002-04-19  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 22:26 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-31 18:05 pme
2002-04-10 10:08 pme
2002-04-09 14:23 bkoz
2001-12-12  9:16 Golubev I. N.

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=20020419052604.836.qmail@sources.redhat.com \
    --to=phil@jaj.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=pme@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).