public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rodrigc@gcc.gnu.org, stanisls@ifi.uio.no
Subject: Re: c++/5845: Seemingly correct code gets "syntax error", but only on gcc 3.0
Date: Tue, 05 Mar 2002 18:06:00 -0000	[thread overview]
Message-ID: <20020306020607.28530.qmail@sources.redhat.com> (raw)

Synopsis: Seemingly correct code gets "syntax error", but only on gcc 3.0

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Tue Mar  5 18:06:06 2002
State-Changed-Why:
    There is a bug in the configure script for Common C++.
    http://cplusplus.sourceforge.net
    
    During the configure, it does not detect the
    <exception> header file:
    
    configure:5784: checking for exception
    configure:5794: gcc -E  conftest.c >/dev/null 2>conftest.out
    configure:5790:21: exception: No such file or directory
    configure: failed program was:
    #line 5789 "configure"
    #include "confdefs.h"
    #include <exception>
    
    Basically the problem is in configure.in:
    
    AC_CHECK_HEADERS(sys/file.h syslog.h posix_evlog.h exception ss.h)    
    
    What happens is, the configure script creates
    a header file with these two lines:
    #include "confdefs.h"
    #include <exception>
    
    and then calls:
    gcc -E
    on that file.
    
    The C compiler doesn't know where the C++ headers are,
    so the test fails.
    
    Can you tell the Common C++ people to improve their
    autoconf test?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5845


             reply	other threads:[~2002-03-06  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05 18:06 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15 19:46 rodrigc
2002-03-05 12:36 stanisls

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=20020306020607.28530.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=stanisls@ifi.uio.no \
    /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).