From: Josh <sundog@mindspring.com>
To: ebotcazou@libertysurf.fr
Cc: gcc@gcc.gnu.org
Subject: Re: Bootstrap failure on Sparc Solaris2.8
Date: Tue, 27 May 2003 17:08:00 -0000 [thread overview]
Message-ID: <8134855.1054054386555.JavaMail.nobody@wamui07.slb.atl.earthlink.net> (raw)
I have now tried to bootstrap with the snapshot dated 20030526, with the same result: eh_alloc.cc fails at line 81, with or without LIBCXXFLAGS set.
I probably shouldn't have, but I did, go in and change the files listed below, commenting out initializations of the __gthread_mutex_t type. This allowed the bootstrap to finish.
In directory libstdc++-v3/include/libsupc++: eh_alloc.cc
In directory libstdc++-v3/include/bits: stl_alloc.h, stl_threads.h
Thanks again.
--Josh
-------Original Message-------
From: Eric Botcazou <ebotcazou@libertysurf.fr>
Sent: 05/23/03 12:05 PM
To: Josh <sundog@mindspring.com>
Subject: Re: Bootstrap failure on Sparc Solaris2.8
>
> > I've configured with the following options in a separate objects
directory
> (gcc-objs), using gcc-3.2.3 as the starting compiler:
../gcc-3.3/configure
> --prefix=/compiler/gcc-3.3 \
> --with-ld=/compiler/gcc-3.2.3/bin/ld
> --with-gnu-ld \
> --with-as=compiler/gcc-3.2.3/bin/as \
> --with-gnu-as \
> --disable-nls \
> --enable-threads=posix
>
> Then:
> make CFLAGS='-O' LIBCFLAGS='-g -O2' LIBCXXFLAGS='-g -O2
> -fno-implicit-templates' boostrap-lean
Did you set CONFIG_SHELL before configuring? Do you use GNU make?
--
Eric Botcazou
>
next reply other threads:[~2003-05-27 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 17:08 Josh [this message]
2003-05-27 17:51 ` Eric Botcazou
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 20:43 Josh Loeb
2003-05-28 20:53 ` Albert Chin
2003-05-27 18:08 Josh
2003-05-27 19:13 ` Eric Botcazou
2003-05-23 13:59 Josh
2003-05-23 16:14 ` Eric Botcazou
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=8134855.1054054386555.JavaMail.nobody@wamui07.slb.atl.earthlink.net \
--to=sundog@mindspring.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@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).