Bug#96539: libstdc++2.10-dev: Error in bastring.h

2001-05-06 Thread Matthias Klose
severity 96539 normal retitle 96539 [fixed in 3.0] libstdc++2.10-dev: Error in bastring.h thanks [EMAIL PROTECTED] writes: > Package: libstdc++2.10-dev > Version: 1:2.95.2-14 > Severity: important wide strings don't work in 2.95.x. See the thread starting at http://gcc.gnu.org/ml/gcc/2000-12/m

Bug#95955: marked as done (gcc-2.95.4: fails to compile glibc, but 2.95.3-11 works)

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 21:34:46 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in gcc-2.95.4-0.010506 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#95969: marked as done (glibc won't build on i386)

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 21:34:46 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in gcc-2.95.4-0.010506 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#95358: marked as done (gpc-2.95 error in prerm)

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 21:34:46 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in gcc-2.95.4-0.010506 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#95978: marked as done (glibc; Fails to build from source)

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 21:34:46 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in gcc-2.95.4-0.010506 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#96436: marked as done (gcc 2.95 package build stomps on dpkg-dev script variables)

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 21:34:46 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in gcc-2.95.4-0.010506 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Processed: Bug#96539: libstdc++2.10-dev: Error in bastring.h

2001-05-06 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 96539 normal Bug#96539: libstdc++2.10-dev: Error in bastring.h Severity set to `normal'. > retitle 96539 [fixed in 3.0] libstdc++2.10-dev: Error in bastring.h Bug#96539: libstdc++2.10-dev: Error in bastring.h Changed Bug title. > thanks Stopp

gcc-2.95_2.95.4.ds1-0.010506_i386.changes INSTALLED

2001-05-06 Thread Debian Installer
Installing: gpc-2.95_2.95.4-0.010506_i386.deb to pool/main/g/gcc-2.95/gpc-2.95_2.95.4-0.010506_i386.deb gobjc-2.95_2.95.4-0.010506_i386.deb to pool/main/g/gcc-2.95/gobjc-2.95_2.95.4-0.010506_i386.deb libg++2.8.1.3-dev_2.95.4-0.010506_i386.deb to pool/main/g/gcc-2.95/libg++2.8.1.3-dev_2.95.4-

gcc-2.95 override disparity

2001-05-06 Thread Debian Installer
There are disparities between your recently installed upload and the override file for the following file(s): libg++2.8.1.3-glibc2.2_2.95.4-0.010506_i386.deb: priority is overridden from extra to optional. Either the package or the override file is incorrect. If you think the override is correc

Re: new gcc-2.95 packages

2001-05-06 Thread Jack Howarth
Matthias, The new gcc-2.95.4 package builds fine on debian ppc woody. Also I am able to now build glibc 2.2.3-1 using the resulting gcc 2.95.4. Jack

Bug#94324: marked as done (g++ cannot compile )

2001-05-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 May 2001 20:13:36 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed in libreadline4-dev-4.2-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#96539: libstdc++2.10-dev: Error in bastring.h

2001-05-06 Thread peter
Package: libstdc++2.10-dev Version: 1:2.95.2-14 Severity: important In bastring.h: const charT* c_str () const { const charT* null_str = ""; if (length () == 0) return null_str; terminate (); return data (); } The second line will _fail_ if charT is not char, which it for instance i

Bug#96436: gcc 2.95 package build stomps on dpkg-dev script variables

2001-05-06 Thread Daniel Jacobowitz
On Sun, May 06, 2001 at 01:36:55PM +0200, Matthias Klose wrote: > > Those names are used -because- dpkg-architecture uses the same names. > > > > More likely this is going wrong: > > ifneq ($(TARGET),native) > > DEB_HOST_ARCH = $(TARGET) > > endif > > > > I see at least two problems: > >

gcc-2.95 build issue -- forwarded message from Roderich Schupp

2001-05-06 Thread Matthias Klose
Matthias Klose writes: > in the changelog you wrote > > * Apparently we do have a problem with dpkg-dev-1.9, which does > >create control files with missing 'Architecture:' lines. Fixes > >are welcome. > > The following patch fixes the problem for a native build, > but will probabl

Bug#96436: gcc 2.95 package build stomps on dpkg-dev script variables

2001-05-06 Thread Matthias Klose
Daniel Jacobowitz writes: > On Sat, May 05, 2001 at 02:50:35PM -0400, Gray Carper wrote: > > Package: gcc-2.95 > > Version: 2.95.4.ds1-0.010424 > > > > In truth, this applies to all gcc-2.95 versions. > > > > When building the gcc-2.95 package, four key dpkg-dev > > variables are utilized

gcc-2.95 build issue -- forwarded message from Roderich Schupp

2001-05-06 Thread Matthias Klose
I missed to forward this message ... --- Begin Message --- Hi, in the changelog you wrote > * Apparently we do have a problem with dpkg-dev-1.9, which does >create control files with missing 'Architecture:' lines. Fixes >are welcome. The following patch fixes the problem for a native bui