This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.2 on Solaris 8 (libgcc_s.so problem)
- From: "Anthony Feick" <afeick at hotmail dot com>
- To: ro at TechFak dot Uni-Bielefeld dot DE
- Cc: rup at kanat dot pair dot com, rschiele at uni-mannheim dot de, gcc at gcc dot gnu dot org, jakub at gcc dot gnu dot org
- Date: Tue, 20 Aug 2002 18:37:03 -0500
- Subject: Re: gcc 3.2 on Solaris 8 (libgcc_s.so problem)
Yes, is seems "binutils 2.13" + "gcc 3.2" + "Solaris 8" => pile of crap. I
still haven't figured out which binutils will work.
I tried the Sun linker and assembler in "/usr/ccs/bin". With them I can at
least run a simple program, but now there are problems linking source files
that use "std::basic_string<wchar_t>".
Hopefully "binutils 2.12.1" will do the trick. If that doesn't work I'll go
back to "binutils 2.11.2"; that worked well with "gcc 3.0.4".
I'm sure I'll get it going eventually. I just found out I need another
configure flag "--enable-cxx-flags="-fshort-wchar". Thank you for your
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: "Anthony Feick" <firstname.lastname@example.org>
CC: email@example.com, firstname.lastname@example.org, email@example.com,
Subject: Re: gcc 3.2 on Solaris 8 (libgcc_s.so problem)
Date: Tue, 20 Aug 2002 17:39:05 +0200 (MEST)
Anthony Feick writes:
> Are you sure these are the 32 bit libraries? I tried just moving them
> local/lib, but libgcc_s.so.1 segfaults instantly.
pretty much so: what does `file' say about them?
> I tried this:
> int main(void)
> return 0;
> When I debug it in gdb I get this:
> Program received signal SIGSEGV, Segmentation fault.
> __register_frame_info_bases (begin=0xff2b0000, ob=0xff2b0000, tbase=0x0,
> at ../../gcc-3.2/gcc/unwind-dw2-fde.c:83
> 83 ob->tbase = tbase;
> Current language: auto; currently c
Did you configure/build with binutils 2.13? I recall reports that these
totally broke gcc 3.2. I've personally avoided GNU binutils on Solaris 2,
and didn't ever have problems with this approach.
Send and receive Hotmail on your mobile device: http://mobile.msn.com