Now that g++ points to g++-4.1 on hppa, is the correct fix here to drop
g++-4.0 and g++-3.4 packages on this architecture?
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL
Steve Langasek writes:
Now that g++ points to g++-4.1 on hppa, is the correct fix here to drop
g++-4.0 and g++-3.4 packages on this architecture?
yes, in the works; additionally all packages depending on libgcc2 have
to be rebuilt.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
OK: it sounds to me like the consensus is that HPPA should move to GCC
4.1 for C++, optionally leaving other languages at GCC 4.0.
Is this acutally decided? Is it likely to happen soon, or should I
build GMP with gcc 3.3 (which doesn't exhibit the problem) in the
short term?
Thanks,
-Steve
--
Is this acutally decided? Is it likely to happen soon, or should I
build GMP with gcc 3.3 (which doesn't exhibit the problem) in the
short term?
For now, I suggest that you remove gcc-4.1 from your build system.
Then, GMP should build fine with 4.0. You might have to reinstall
4.0.
As far
On Sun, Apr 30, 2006 at 06:53:03PM -0400, John David Anglin wrote:
Is this acutally decided? Is it likely to happen soon, or should I
build GMP with gcc 3.3 (which doesn't exhibit the problem) in the
short term?
For now, I suggest that you remove gcc-4.1 from your build system.
Then, GMP
On Sat, Apr 22, 2006 at 11:22:20AM -0400, John David Anglin wrote:
...
I recognized that this was going to cause pain, and brought the matter
up for discussion on the parisc-linux list a few months ago. There
wasn't much in the way of comments for or against. In the end, I
decided it was
$ ldd a.out
libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x40575000)
libm.so.6 = /lib/libm.so.6 (0x4046e000)
libgcc_s.so.2 = /lib/libgcc_s.so.2 (0x40068000)
libc.so.6 = /lib/libc.so.6 (0x4074b000)
libgcc_s.so.4 = /lib/libgcc_s.so.4 (0x40015000)
On Sat, Apr 22, 2006 at 10:00:04AM +0200, Matthias Klose wrote:
$ ldd a.out
libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x40575000)
libm.so.6 = /lib/libm.so.6 (0x4046e000)
libgcc_s.so.2 = /lib/libgcc_s.so.2 (0x40068000)
libc.so.6 = /lib/libc.so.6 (0x4074b000)
On Sat, Apr 22, 2006 at 10:00:04AM +0200, Matthias Klose wrote:
$ ldd a.out
libstdc++.so.6 =3D /usr/lib/libstdc++.so.6 (0x40575000)
libm.so.6 =3D /lib/libm.so.6 (0x4046e000)
libgcc_s.so.2 =3D /lib/libgcc_s.so.2 (0x40068000)
libc.so.6 =3D /lib/libc.so.6
[EMAIL PROTECTED]:~/gmp-4.2.dfsg/tests/cxx$ g++ -Wall test-throw.cc
./a.out
/usr/bin/ld: warning: libgcc_s.so.4, needed by
/usr/lib/gcc/hppa-linux-gnu/4.0.3/libstdc++.so, may conflict with
libgcc_s.so.2
I'm puzzled about this. It seems like libstdc++ for GCC 4.0.3 was
built using
John David Anglin writes:
[EMAIL PROTECTED]:~/gmp-4.2.dfsg/tests/cxx$ g++ -Wall test-throw.cc
./a.out
/usr/bin/ld: warning: libgcc_s.so.4, needed by
/usr/lib/gcc/hppa-linux-gnu/4.0.3/libstdc++.so, may conflict with
libgcc_s.so.2
I'm puzzled about this. It seems like
Yes, we do, but
$ ls -l /usr/lib/gcc/hppa-linux-gnu/4.0.3/libstdc++.so
lrwxr-xr-x 1 root root 23 Apr 6 02:08
/usr/lib/gcc/hppa-linux-gnu/4.0.3/libstdc++.so - ../../../libstdc++.so.6
Oh, I was thinking there were separate libraries for each GCC version.
I've had to live with this for some
Package: g++-4.0
Version: 4.0.3-1
Severity: grave
Hi,
Ignore the architecture below -- this report is about HPPA.
Here's a simple program that runs fine on my x86 box, but fails
on Paer (2.6.16-1-parisc64-smp #2 SMP).
[EMAIL PROTECTED]:~/gmp-4.2.dfsg/tests/cxx$ cat test-throw.cc
#include
13 matches
Mail list logo
