Matthias Klose wrote:
[should we drop parisc-linux?]
John David Anglin writes:
Er, no; we're talking about official Debian packages here, and the
libstdc++.so.6 in Debian is now from gcc-4.1. The problem is precisely that
GMP *is* being built using gcc-4.0, but libstdc++ is from gcc-4.1, resul
> Ok, coming back to the question of the system compiler on hppa for
> etch. Assuming that hppa does want to do that:
>
> - is glibc buildable with gcc-4.1 on hppa?
As far as I know, there's no new problems using 4.1 instead of 4.0. See
http://lists.parisc-linux.org/pipermail/parisc-linux/2006-A
[should we drop parisc-linux?]
John David Anglin writes:
> > Er, no; we're talking about official Debian packages here, and the
> > libstdc++.so.6 in Debian is now from gcc-4.1. The problem is precisely that
> > GMP *is* being built using gcc-4.0, but libstdc++ is from gcc-4.1, resulting
> > in t
> Er, no; we're talking about official Debian packages here, and the
> libstdc++.so.6 in Debian is now from gcc-4.1. The problem is precisely that
> GMP *is* being built using gcc-4.0, but libstdc++ is from gcc-4.1, resulting
> in the double libgcc_s problem.
Then, you must build *eveything* for
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.
> Th
> 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 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
> 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
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 s
> > [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
bu
> 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> /li
11 matches
Mail list logo
