Bug#105741: not fixed

2002-05-29 Thread Eduard Bloch
Moin Matthias! Matthias Klose schrieb am Thursday, den 30. May 2002: > allegro now is at version 4.0. Please could you try to reproduce the > behaviour with this version? Please could you try to recompile with > gcc-3.1 (unstable)? Works with gcc-3.1. I am impressed, all bugs I have found in gc?-

Re: GCC 3.2 transition

2002-08-18 Thread Eduard Bloch
#include * Matthew Wilcox [Fri, Aug 16 2002, 02:51:34PM]: >Because upstream chooses the soname to match their API. If we change Do we know this? >the soname then we render ourselves binary-incompatible with other >distros and vendor-supplied binaries. This is important because the

Re: Yet another stupid suggestion (Re: GCC 3.2 transition )

2002-08-19 Thread Eduard Bloch
#include * Allan Sandfeld Jensen [Mon, Aug 19 2002, 02:58:06PM]: > libraries are placed under /usr/lib/g++2.95 and the new ones under > /usr/lib/g++3.1. The defaults are symbolic linked from /usr/lib. We can > either hack ld.so to search the correct path (using some g++ calling cards) > or reco

Bug#485135: To fail or misbehave

2008-07-18 Thread Eduard Bloch
> Please explain. In C++ there is no implicit conversion between int and > char *. Exactly. So if you check the return value then the compiler will fail (like in the test case above) and you are lucky to notice the problem. But if you don't check it and rely on the function to do what it has to

Bug#485135: To fail or misbehave

2008-07-19 Thread Eduard Bloch
#include * Bastian Blank [Fri, Jul 18 2008, 03:37:39PM]: > > But if you don't check it and rely on the function to do what it has > > to do (i.e. write the result into the buffer in the argument) then you > > silently get a buffer with undefined data back (most likely > > unchanged). > > No. You

Bug#382748: BTW, bug 382748 requires new binaries

2007-01-07 Thread Eduard Bloch
#include * Albert Cahalan [Sun, Aug 13 2006, 01:22:44AM]: > I forgot to point out: > > Once this is fixed, all powerpc packages need > to be rebuilt ASAP. Would you also care to explain why? What exactly does not having this options working make the compilation products unreleaseable? Eduard. -

Bug#285692: internal compiler error: in tree_low_cst, at tree.c:3255

2004-12-14 Thread Eduard Bloch
Package: g++-3.4 Version: 3.4.3-4 Severity: normal Hello, have trouble compiling a software package (MCA, mca2.sf.net with local extensions) using Debian's g++. There was no such problem compiling on Gentoo (g++ 3.3.3), so I report it here as Debian specific issue. The problem appears with the f

Bug#194345: FTB the lufs package

2003-10-21 Thread Eduard Bloch
severity 194345 grave tag 194345 + sid thanks It became worse. The last version cannot build my lufs package because of the astronomical memory usage. Even 2GB of virtual memory isn't enough. MfG, Eduard. -- Letzte Worte eines Turmspringers: "Heute ist das Wasser aber klar!"

Bug#194345: [edi@gmx.de: Re: Bug#194345: FTB the lufs package]

2003-10-22 Thread Eduard Bloch
Forgotten copy; the file is stored on http://people.debian.org/~blade/misc/sshfs-breaks-with-g++-3.3.tgz - Forwarded message from Eduard Bloch <[EMAIL PROTECTED]> - Date: Wed, 22 Oct 2003 11:28:47 +0200 From: Eduard Bloch <[EMAIL PROTECTED]> Subject: Re: Bug#194345: FTB the

Bug#105741: gcc-3.0 misscompiles the Allegro library

2001-07-18 Thread Eduard Bloch
Package: gcc-3.0 Version: 1:3.0-4 Severity: normal S.s. You can take allegro3937 from incoming.d.o. or from ftp-mirrors when it is installed. gcc-3.0 can compile binaries and link to the existing liballegro*.so without any problems, but when compiling the library itself, the result is broken. Any

Bug#105741: PS

2001-07-18 Thread Eduard Bloch
Errr: | Note: this breakage also appears on i386, other plattform seems not to | be affected. Should be: this breakage seems to appear only on i386... -- Heute kann man ja kaum noch eine AOL-CD aus dem Fenster werfen, ohne jemanden zu treffen, der einen SuSE-Karton unter dem Arm trägt.

Bug#105741: not fixed

2001-10-16 Thread Eduard Bloch
reopen 105741 thanks > * Update to CVS sources (011014). Frozen for upstream 3.0.2 release. > Closes: #109351, #114099, #114216, #105741 (allegro3938). Nope, still misscompiles the shared library. Gruss/Regards, Eduard. -- "NT ist auch ein UNIX - es ist ja schließlich in C geschrieben."

Bug#116128: gcj-3.0: FileWriter problems

2001-10-18 Thread Eduard Bloch
braries an ii libgcj2-dev 1:3.0.2-0pre011014 Java development headers and stati ii zlib1g1:1.1.3-16 compression library - runtime -- Akkulicht-Radler! Foliengriller! Anonymspender! Vorfahrtverzichter! /* Eduard Bloch <[EMAIL PROTECTED]>, 2001 Demo

Bug#116128: gcj-3.0: FileWriter problems

2001-10-18 Thread Eduard Bloch
Moin Matthias! Matthias Klose schrieb am Donnerstag, den 18. Oktober 2001: > > gcj-3.0 -g fromFileToFile.java --main=fromFileToFile ... > > And if I change the Exception to IOExcepion (as it should be), it > > crashes or exits. > > did it build with an old version? It builds fine, the errors occ

Bug#260248: unable to link with -lsupc++

2004-07-19 Thread Eduard Bloch
Package: gcc-3.4 Version: 3.4.0-4 Severity: important Hello, few packages (at least icewm and rxvt-unicode) use gcc to link C++ applications that do not require special libstdc++ features (resulting in avoiding a useless dependency). However, gcc-3.4 fails to link with -lsupc++ for unknown reason