Re: gcc 3.1 as default Debian compiler

2002-06-10 Thread Philip Blundell
On Mon, 2002-06-10 at 22:04, Chris Cheney wrote: > Does anyone know if/when Debian is planning on switching the default > compiler to gcc 3.1.x. I am waiting to upload KDE 3 to see if gcc 3.1 > will become the default compiler anytime soon. At some point during the next major release cycle, yes.

Re: gcc 3.1 as default Debian compiler

2002-06-10 Thread Martin v. Loewis
Chris Cheney <[EMAIL PROTECTED]> writes: > Does anyone know if/when Debian is planning on switching the default > compiler to gcc 3.1.x. I am waiting to upload KDE 3 to see if gcc 3.1 > will become the default compiler anytime soon. Perhaps never. For the upcoming Debian release, the compiler wi

gcc 3.1 as default Debian compiler

2002-06-10 Thread Chris Cheney
Does anyone know if/when Debian is planning on switching the default compiler to gcc 3.1.x. I am waiting to upload KDE 3 to see if gcc 3.1 will become the default compiler anytime soon. Thanks, Chris Cheney I am not subscribed to this list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#149561: bad pathnames coded into the libs

2002-06-10 Thread Daniel Jacobowitz
On Mon, Jun 10, 2002 at 09:03:14AM -0400, Phil Edwards wrote: > On Mon, Jun 10, 2002 at 02:15:35PM +0200, Ulrich Eckhardt wrote: > > While trying to debug a program, I encountered some weird paths that > > prevented me from taking advance of the debug-lib: > > > > LD_PRELOAD=/usr/lib/libstdc++_de

Bug#149555: no documentation on how to use the lib for debugging

2002-06-10 Thread Daniel Jacobowitz
On Mon, Jun 10, 2002 at 01:53:45PM +0200, Ulrich Eckhardt wrote: > Package: libstdc++3-dbg > Version: 3.0.4-7 > > There is not a single note on how to use the lib for debugging, eg > setting: > LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++.so.3 > before starting the program to be debugged or exp

Bug#149561: bad pathnames coded into the libs

2002-06-10 Thread Phil Edwards
On Mon, Jun 10, 2002 at 02:15:35PM +0200, Ulrich Eckhardt wrote: > While trying to debug a program, I encountered some weird paths that > prevented me from taking advance of the debug-lib: > > LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test > ... > (gdb) step > 178 in > /home/

Processed: Re: Bug#149555: no documentation on how to use the lib for debugging

2002-06-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 149555 wishlist Bug#149555: no documentation on how to use the lib for debugging Severity set to `wishlist'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator

Bug#149561: bad pathnames coded into the libs

2002-06-10 Thread Philip Blundell
On Mon, 2002-06-10 at 13:15, Ulrich Eckhardt wrote: > Package: libstdc++3-dbg > Version: 3.0.4-7 > > While trying to debug a program, I encountered some weird paths that > prevented me from taking advance of the debug-lib: > > LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test > ...

Bug#149561: bad pathnames coded into the libs

2002-06-10 Thread Ulrich Eckhardt
Package: libstdc++3-dbg Version: 3.0.4-7 While trying to debug a program, I encountered some weird paths that prevented me from taking advance of the debug-lib: LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++3.so.3 gdb ./test ... (gdb) step 178 in /home/doko/packages/gcc/3.0/gcc-3.0-3.0.4ds3/

Bug#149555: no documentation on how to use the lib for debugging

2002-06-10 Thread Ulrich Eckhardt
Package: libstdc++3-dbg Version: 3.0.4-7 There is not a single note on how to use the lib for debugging, eg setting: LD_PRELOAD=/usr/lib/libstdc++_debug/libstdc++.so.3 before starting the program to be debugged or explicitly linking with that lib (untested): $(CXX) ... -l/usr/lib/libstdc++_de