public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9249: Solaris 8: bootstrap fails with --enable-__cxa-atexit
Date: Fri, 10 Jan 2003 09:56:00 -0000 [thread overview]
Message-ID: <20030110095603.8165.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9249; it has been noted by GNATS.
>From cludwig@cdc.informatik.tu-darmstadt.de Mon Jan 13 00:47:57 2003
From: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de>
To: Phil Edwards <phil@jaj.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/9249: Solaris 8: bootstrap fails with --enable-__cxa-atexit
Date: Fri, 10 Jan 2003 10:49:53 +0100
Hi,
On Thu, Jan 09, 2003 at 05:57:46PM -0500, Phil Edwards wrote:
> On Thu, Jan 09, 2003 at 04:24:28PM -0000, cludwig@cdc.informatik.tu-darmstadt.de wrote:
> __cxa_atexit is part of glibc, not SUN's libc. You can't use it if it's
> not there.
Good point. :-) But let me change the PR into a feature and
documentation request:
a) http://gcc.gnu.org/install/configure.html does not mention
--enable-__cxa-atexit at all. I found it only when I ran
`gcc/configure --help'. I guess you need to supply this option if
you want to use the compiler option -fuse-cxa-atexit?
Or does it make -fuse-cxa-atexit the default?
b) configure should complain if --enable-__cxa-atexit was passed but
is not supported rather than produce linker errors at the end of
the build process.
Nevertheless, thanks for the clarification!
Regards
Christoph
--
http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html
LiDIA-CA: http://www.informatik.tu-darmstadt.de/TI/Forschung/LiDIA-CA/
next reply other threads:[~2003-01-10 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 9:56 Christoph Ludwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 23:06 Phil Edwards
2003-01-09 16:26 cludwig
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=20030110095603.8165.qmail@sources.redhat.com \
--to=cludwig@cdc.informatik.tu-darmstadt.de \
--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).