Bug#151618: g++-3.1: Rope apparently moved out of std.

2002-07-01 Thread elf
I suspected that, but using namespace __gnu_cxx; reports that the namespace '__gnu_cxx' is undeclared. Explicitly referencing that namespace does work. On Mon, Jul 01, 2002 at 06:59:25PM -0400, Phil Edwards wrote: > On Mon, Jul 01, 2002 at 10:44:16PM -, Marc Singer wrote: > > Package: g++

Re: GCC-3.0, -static, and -shared-libgcc

2002-01-20 Thread elf
I believed I tested a case that I had not. I was using -Wl to set the linker switches. This won't work any more. Using the switches directly with gcc-3.0 works properly. gcc-3.0 -static versus gcc-3.0 -Wl,-static Thanks. On Sun, Jan 20, 2002 at 07:28:55PM -0500, Ben Collins wrote: > >

Re: GCC-3.0, -static, and -shared-libgcc

2002-01-20 Thread elf
On Sun, Jan 20, 2002 at 05:32:49PM -0500, Ben Collins wrote: > > > The error seems to be in the specs file. In mine, I have: > > > > > > *libgcc: > > > %{shared-libgcc:-lgcc_s%M > > > -lgcc}%{static-libgcc:-lgcc}%{!shared-libgcc:%{!static-libgcc:%{shared:-lgcc_s%M > > > -lgcc}}}%{!shared-libgcc:

Re: GCC-3.0, -static, and -shared-libgcc

2002-01-20 Thread elf
On Sun, Jan 20, 2002 at 04:53:20PM -0500, Ben Collins wrote: > > This fails > > > > g++-3.0 -o bin/program o/object1.o ... -static > > > > because gcc-3.0 cannot find the libgcc_s.a file. > > > > /usr/bin/ld: cannot find -lgcc_s > > It shouldn't be looking for libgcc_s.a, it should use libg

GCC-3.0, -static, and -shared-libgcc

2002-01-20 Thread elf
It appears that the command line I use in gcc-2.9x for building s static version of a program fails with gcc-3.0. It also appears, from the documentation, that there is a switch to make it work anyway. This works with the 2.9x version. g++ -o bin/program o/object1.o ... -static This fails