public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Molloy <jamesmol@transitive.com>
To: gcc-help@gcc.gnu.org
Subject: GCC 4.3.0 configure failure: libgcc
Date: Tue, 06 May 2008 14:27:00 -0000	[thread overview]
Message-ID: <48206A25.5060304@transitive.com> (raw)

Hi,

I'm attempting to build GCC 4.3.0 - and I thought I had succeeded until 
I realised that the 'all-gcc' make target (now?) doesn't build libgcc.a.

So I'm now trying to make the 'all' target, and I'm getting a configure 
error in the libgcc directory. An extract of the config.log follows:

    configure:4082: g++ -c -g -O2  conftest.cc >&5
    conftest.cc: In function 'int main()':
    conftest.cc:13: error: 'exit' was not declared in this scope
    configure:4088: $? = 1
    configure: failed program was:
    | /* confdefs.h.  */
    |
    | #define PACKAGE_NAME ""
    | #define PACKAGE_TARNAME ""
    | #define PACKAGE_VERSION ""
    | #define PACKAGE_STRING ""
    | #define PACKAGE_BUGREPORT ""
    | /* end confdefs.h.  */
    |
    | int
    | main ()
    | {
    | exit (42);
    |   ;
    |   return 0;
    | }

As you can see, the test program autoconf is generating does not include 
<cstdlib>, so g++ is perfectly correct in erroring.

I'm not certain how to fix this - is it just a case of hacking the 
config.in file? I'd appreciate any help.

Compiling GCC 4.3.0 from source using G++ 4.1.2, autoconf 2.61, and 
automake 1.10.

Thanks,

James

             reply	other threads:[~2008-05-06 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 14:27 James Molloy [this message]
2008-05-06 23:25 ` Ralf Wildenhues
2008-05-07  8:16   ` James Molloy
2008-05-07 21:06     ` gcc 4.2.x large file support Jonathan Saxton
2008-05-08  7:31       ` Michael Haubenwallner

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=48206A25.5060304@transitive.com \
    --to=jamesmol@transitive.com \
    --cc=gcc-help@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).