public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: matt zagrabelny <mzagrabe@d.umn.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9518: apparent header file problems
Date: Mon, 03 Feb 2003 01:46:00 -0000	[thread overview]
Message-ID: <20030203014601.19396.qmail@sources.redhat.com> (raw)

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

From: matt zagrabelny <mzagrabe@d.umn.edu>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mzagrabe@d.umn.edu, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/9518: apparent header file problems
Date: 02 Feb 2003 19:40:42 -0600

 the install was done via debian packages (dselect from the unstable
 branch to be specific). simple c programs compile, but compiling the
 kernel results in a segmentation fault as well (i have not submitted a
 bug report for that yet.) this program fails every compile. i dont know
 what else to do, i have tried purging and reinstalling certain packages
 (and shaking my fists at the monitor) but i do not know enough to do any
 serious debugging. let me know if there is anything i could try (to help
 debugging).
 
 -matt
 
 On Sun, 2003-02-02 at 16:37, bangerth@dealii.org wrote:
 > Synopsis: apparent header file problems
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Sun Feb  2 22:37:18 2003
 > State-Changed-Why:
 >     I cannot reproduce this with today's 3.2.2 CVS:
 >     tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -c x.cc
 >     x.cc: In function `int main(int, char**)':
 >     x.cc:4: `cout' undeclared (first use this function)
 >     x.cc:4: (Each undeclared identifier is reported only once for each function it
 >        appears in.)
 >     x.cc:4: `endl' undeclared (first use this function)
 >     
 >     Can you say something about how you installed your
 >     compiler? I suspect that this must be something specific
 >     to your installation, since none of us can reproduce
 >     the problem.
 >     
 >     Regards
 >       Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9518
 
 


             reply	other threads:[~2003-02-03  1:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03  1:46 matt zagrabelny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 17:12 bangerth
2003-02-03  6:46 Christian Ehrhardt
2003-02-03  1:26 matt zagrabelny
2003-02-02 22:37 bangerth
2003-02-02  9:16 ehrhardt
2003-02-01 22:39 ehrhardt
2003-01-31  5:06 mzagrabe

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=20030203014601.19396.qmail@sources.redhat.com \
    --to=mzagrabe@d.umn.edu \
    --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).