Bug#430395: gcc-4.2 FTBFS when cross compiling because of wrong config path in binary-libstdcxx-cross.mk

2007-06-25 Thread Arthur Loiret
Package: gcc-4.2 Version: 4.2-20070609 Hello, The file libstdc++-v3/config/linker-map.gnu has moved in gcc-4.2 to libstdc++-v3/config/abi/pre/gnu.ver, then I suggest to correct the path in binary-libstdcxx-cross.mk. A simple patch is joined, and I have successfully built gcc-4.2 for several

Processed: [bts-link] source package gcc-snapshot

2007-06-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report

Processed: Re: libstdc++6: can't construct a locale with empty string, violation of the C++ standard

2007-06-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 429660 libstdc++6 Bug#429660: g++-4.2: program using locales segfaults when compile with locales Bug reassigned from package `g++-4.2' to `libstdc++6'. merge 429660 429882 Bug#429660: g++-4.2: program using locales segfaults when compile

Bug#430395: (pas de sujet)

2007-06-25 Thread Arthur Loiret
Here is the error I got: cp -p /usr/src/gcc-4.2/gcc-4.2-4.2-20070609/src/libstdc++-v3/config/linker-map.gnu \ debian/libstdc++6-4.2-pic-sparc-cross/usr/lib/gcc/sparc-linux-gnu/4.2.1/libstdc++_pic.map cp: cannot stat `/usr/src/gcc-4.2/gcc-4.2-4.2-20070609/src/libstdc++-v3/config/linker-map.gnu':

Reverting r2000 for gcc-4.2

2007-06-25 Thread Matthias Klose
Ludovic, I'll revert this checkin on the 4.2 branch. Without it we only apply and test the patches for specific builds and architectures. This then tends to be discovered on the build daemons, which is late. Adjusting the build dependencies is certainly ok. Matthias -- To UNSUBSCRIBE,

Processed: [bts-link] source package gcc-snapshot

2007-06-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report

Re: Reverting r2000 for gcc-4.2

2007-06-25 Thread Ludovic Brenta
Matthias Klose writes: I'll revert this checkin on the 4.2 branch. Without it we only apply and test the patches for specific builds and architectures. This then tends to be discovered on the build daemons, which is late. Adjusting the build dependencies is certainly ok. OK, that's why this

Processed: forwarded gcc report

2007-06-25 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: forwarded 428926 http://gcc.gnu.org/PR32509 Bug#428926: gmp: FTBFS: /usr/include/c++/4.1.3/bits/locale_facets.h:1682: undefined reference to `std::numpunctchar::_M_initialize_numpunct(__locale_struct*)' Noted your statement that Bug has been forwarded

[Bug libstdc++/32509] [4.1 regression ?] fails to link using -O

2007-06-25 Thread pcarlini at suse dot de
--- Comment #1 from pcarlini at suse dot de 2007-06-25 23:03 --- Whatever it is, it isn't a libstdc++ proper issue: the 4_1-branch is in deep regressions-only mode, only very few commits to the breanch during the last 6+ months, nothing related to that issue (just have a look to the

[Bug libstdc++/32509] [4.1 regression ?] fails to link using -O

2007-06-25 Thread pcarlini at suse dot de
--- Comment #2 from pcarlini at suse dot de 2007-06-25 23:13 --- And of course a normally installed and configured recent 4_1-branch gcc (20070619) compiles the provided snippet just fine. The symbol is exported as expected: 000ad570 T

[Bug libstdc++/32509] [4.1 regression ?] fails to link using -O

2007-06-25 Thread pcarlini at suse dot de
--- Comment #3 from pcarlini at suse dot de 2007-06-25 23:27 --- Sorry, disregard my remark between parentheses about 4.1 headers vs 4.2 library, I didn't follow your way of explaining your setup: yes, actaully, a 4.1 object *can* be linked to a 4.2 *.so. In any case, certainly the