public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Does C++ std::queue really conflict with C header 'struct queue'?
Date: Wed, 30 Jul 2003 20:14:00 -0000	[thread overview]
Message-ID: <20030730195351.GA14160@disaster.jaj.com> (raw)
In-Reply-To: <20030726042529.GA906@twcny.rr.com>

On Sat, Jul 26, 2003 at 12:25:29AM -0400, Nathanael Nerode wrote:
> I doubt that Solaris comes out of config.guess as "*-*-svr4*", though, 

It doesn't.

> so I think it doesn't use the fixinc.svr4 script, the only one
> which still has that fix.

How do I check?


> If this is essentially the same case, you could try removing *that* fix
> (hackname 'math_exception').  (I can't check that either, since my only 
> machine uses glibc, which already has essentially incorporated the 
> fixincludes fix into its math.h.)

I removed both the queue and the exception fixes, and bootstrap+test didn't
behave any differently.  Which, as you say, probably means the file wasn't
even being looked at.  :-)


Phil

-- 
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:[~2003-07-30 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 12:42 Nathanael Nerode
2003-07-30 20:14 ` Phil Edwards [this message]
2003-07-30 23:31   ` Nathanael Nerode
  -- strict thread matches above, loose matches on Subject: below --
2003-07-26  5:16 Nathanael Nerode
2003-07-26 12:08 ` Phil Edwards

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=20030730195351.GA14160@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.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).