Bug#195468: g++-3.3: default construction fails when no explicit default constructor defined

2003-05-30 Thread Herbert Valerio Riedel
On Fri, 2003-05-30 at 22:08, Phil Edwards wrote: > On Fri, May 30, 2003 at 09:26:32PM +0200, Herbert Valerio Riedel wrote: > > $ cat static_var.cc > > > > class bar { > > public: > > int operator()(int i) { return i; } > > //bar (void) {} // default constructor > > }; > > > > const bar b = ba

Processed: Those bugs are about gcj as well

2003-05-30 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > clone 195351 -1 Bug#195351: libsablevm1-dev conflicts with gcj Bug 195351 cloned as bug 195483. > clone 195350 -2 Bug#195350: libgcj4 and libsablevm1-dev both include /usr/include/jni.h Bug 195350 cloned as bug 195484. > reassign -1 libgcj4-dev Bug#19

Bug#195480: gcj-3.3 thinks a decl conflicts with itself

2003-05-30 Thread Yann Dirson
Package: gcj-3.3 Version: 1:3.3-2 Severity: normal Build log is quite short: | tau-2.12.8/tools/src/jRacy$ LC_ALL=C gcj-wrapper-3.3 *.java | DB.java:9: warning: Discouraged redundant use of `public' modifier in declaration of abstract method `connect'. |public boolean connect(DBAcct acct

Bug#195468: g++-3.3: default construction fails when no explicit default constructor defined

2003-05-30 Thread Phil Edwards
On Fri, May 30, 2003 at 09:26:32PM +0200, Herbert Valerio Riedel wrote: > $ cat static_var.cc > > class bar { > public: > int operator()(int i) { return i; } > //bar (void) {} // default constructor > }; > > const bar b = bar (); // works always... > const bar b2; // fails if there is no expl

Bug#195468: g++-3.3: default construction fails when no explicit default constructor defined

2003-05-30 Thread Herbert Valerio Riedel
Package: g++-3.3 Version: 1:3.3-2 Severity: normal I'm not sure, whether this should work according to the ISO C++ specs or not; IMHO it should work... :-) $ cat static_var.cc class bar { public: int operator()(int i) { return i; } //bar (void) {} // default constructor }; const bar b = ba

Bug#195388:

2003-05-30 Thread Herbert Valerio Riedel
...just found out, that this is a non-bug; please close this bug http://www.research.att.com/~bs/3rd_printing11.html > pg 489 replace "Erasing end() is harmless." by "A call m.erase(b,e) > where e is m.end() is harmless (provided b refers to an element of m > or is m.end()). However, a call m.era

Bug#195424: [3.3 -O2 arm regression] seg fault when compiling xfree86

2003-05-30 Thread James Troup
Package: gcc-3.3 Version: 3.3-2 Severity: important This is a regression from 2.95 and 3.2; there doesn't seem to be a recent gcc-snapshot package to test with. Compiling with -O1 makes the ICE go away. -save-temps output available here: http://people.debian.org/~troup/gcc/Xrm.i.bz2 (It's 312k

Bug#195388: libstdc++5-3.3-dev: erase()ing end() not harmless

2003-05-30 Thread Herbert Valerio Riedel
Package: libstdc++5-3.3-dev Version: 1:3.3-2 Severity: normal ...according to TC++PL 3rd ed, section 17.4.1.7, "Erasing end() is harmless." but the following code either hangs or crashes when the end() iterator is being passed to erase(); *** set_erase.cc #include #include #include int ma

Bug#195369: gcc-3.3 seems to need a versioned build dependency on a doxygen

2003-05-30 Thread Matthias Klose
Adrian Bunk writes: > Package: gcc-3.3 > Version: 1:3.3-2 > Severity: normal > > > Building gcc-3.3 on a woody system with some additional updates produces > the following messages: > > <-- snip --> > > It seems a versioned build dependency on doxygen is needed > (but hopefully no build depen

Bug#195369: gcc-3.3 seems to need a versioned build dependency on a doxygen

2003-05-30 Thread Adrian Bunk
Package: gcc-3.3 Version: 1:3.3-2 Severity: normal Building gcc-3.3 on a woody system with some additional updates produces the following messages: <-- snip --> ... make[2]: Entering directory `/home/bunk/Pakete/gcc-3.3/gcc-3.3-3.3ds9/build/i386 -linux/libstdc++-v3' (srcdir=`cd ../../../src/l

Bug#195353: java.net.SocketException: SO_REUSEADDR: not valid for TCP

2003-05-30 Thread Martin v. Löwis
Adam Heath <[EMAIL PROTECTED]> writes: > java.net.SocketException: SO_REUSEADDR: not valid for TCP [...] > It is perfectly fine to set that option for a tcp socket. Setting it for > udp makes no sense. Hmm. http://java.sun.com/j2se/1.4.1/docs/api/java/net/SocketOptions.html#SO_REUSEADDR says S

Bug#195348: marked as done (libgcj.jar is missing LinkedHashMap)

2003-05-30 Thread Debian Bug Tracking System
Your message dated Thu, 29 May 2003 23:35:16 -0500 (CDT) with message-id <[EMAIL PROTECTED]> and subject line Bug#195348: Acknowledgement (libgcj.jar is missing LinkedHashMap) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.