Bug#190066: gcc-3.3: missing support for x86-64

2003-04-21 Thread Arnd Bergmann
On Monday 21 April 2003 22:59, Matthias Klose wrote: > Arnd Bergmann writes: > > See also Bug#189350 for the required binutils patch.# ignore 64 bit > > shlibdeps for now, as on s390 and sparc64 > > you do this for libgcc1 and libstdc++5 only. Yes, that was an accident. > maybe it's time to build

Bug#190066: gcc-3.3: missing support for x86-64

2003-04-21 Thread Matthias Klose
Arnd Bergmann writes: > > See also Bug#189350 for the required binutils patch.# ignore 64 bit shlibdeps > for now, as on s390 and sparc64 you do this for libgcc1 and libstdc++5 only. maybe it's time to build extra "64" packages. Is there already a naming convention for these packages (i.e. libgc

Bug#190066: gcc-3.3: missing support for x86-64

2003-04-21 Thread Arnd Bergmann
Package: gcc-3.3 Version: 1:3.3ds5-0pre5 Tags: patch In order to start a Debian x86-64 port, we need a compiler that can create 64 bit binaries. The attached patch makes the i386 gcc-3.3 package bi-arch capable, similar to the respective sparc and s390 packages. It also adds x86_64 libraries for t

Re: TLS. nptl and gcc/glibc/binutils

2003-04-21 Thread Daniel Jacobowitz
On Mon, Apr 21, 2003 at 05:51:37AM -0700, Jeff Bailey wrote: > On Mon, Apr 21, 2003 at 02:18:01PM +0900, GOTO Masanori wrote: > > > > My thought is that gcc-3.3 will be out soon enough for us to use that. > > > But for future coming stable gcc-3.3, we should start to support tls > > and nptl, an

Re: TLS. nptl and gcc/glibc/binutils

2003-04-21 Thread Jeff Bailey
On Mon, Apr 21, 2003 at 02:18:01PM +0900, GOTO Masanori wrote: > > My thought is that gcc-3.3 will be out soon enough for us to use that. > But for future coming stable gcc-3.3, we should start to support tls > and nptl, and I already start to investigate. I think we should have > two libc6: li

Bug#189983: libstdc++5: symbol __gnu_cxx::_Atomic_add_mutex missing

2003-04-21 Thread Simon Hausmann
Package: libstdc++5 Version: 1:3.3-0pre5 Severity: normal The symbol in the subject is missing from libstdc++5. It appears to be new in gcc-3.3's libstdc++. A simple testcase like this compiled with -O2 reproduces the problem: #include int main() { std::string bleh; return 0; } g++-3.3

gcc-3.3_3.3ds5-0pre5_arm.changes ACCEPTED

2003-04-21 Thread Debian Installer
Accepted: cpp-3.3_3.3-0pre5_arm.deb to pool/main/g/gcc-3.3/cpp-3.3_3.3-0pre5_arm.deb fastjar_3.3-0pre5_arm.deb to pool/main/g/gcc-3.3/fastjar_3.3-0pre5_arm.deb fixincludes_3.3-0pre5_arm.deb to pool/main/g/gcc-3.3/fixincludes_3.3-0pre5_arm.deb g++-3.3_3.3-0pre5_arm.deb to pool/main/g/gcc-3.

Processed: Re: Bug#189658: cpp-3.2: cpp package won't install

2003-04-21 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 189658 cpp Bug#189658: cpp-3.2: cpp package won't install Bug reassigned from package `cpp-3.2' to `cpp'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, D

Bug#189658: cpp-3.2: cpp package won't install

2003-04-21 Thread Matthias Klose
reassign 189658 cpp thanks I doubt this is a bug in the package. Please could you compare the downloaded package with the one at http://packages.debian.org/unstable/interpreters/cpp.html Can you reproduce this behaviour on another machine? Herbert Buurman writes: > Package: cpp-3.2 > Version: 1:

Bug#189851: FTBFS on hurd-i386

2003-04-21 Thread Matthias Klose
Michael Banck writes: > Package: gcc-3.3 > Version: 1:3.3ds5-0pre5 > Severity: important > > After adding hurd-i386 to pascal_no_archs, the packages seem to have > gotten created successfully, I did not test them yet. > > I tried to find out where binobj.1 get created, but got lost in the > buil

Re: TLS. nptl and gcc/glibc/binutils

2003-04-21 Thread GOTO Masanori
At Sun, 20 Apr 2003 18:45:15 -0700, Jeff Bailey wrote: > > On Sun, Apr 20, 2003 at 12:51:43PM -0400, Jack Howarth wrote: > > >I am wondering if there is a gameplan on adding the support for > > enabling TLS support in the devtools in sid. In particular, in trying > > to build the current debi