Bug#564984: marked as done (fauhdlc: ftbfs with gcc-4.5)
Your message dated Tue, 22 Jun 2010 13:46:40 +0200 with message-id <4c20a2a0.3020...@debian.org> and subject line Re: Bug#564984: fauhdlc: ftbfs with gcc-4.5 has caused the Debian Bug report #564984, regarding fauhdlc: ftbfs with gcc-4.5 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 your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 564984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fauhdlc Version: 20091119-1 Severity: normal Tags: sid User: debian-gcc@lists.debian.org Usertags: ftbfs-gcc-4.5 The package fails to build in a test rebuild on at least amd64 with gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4. For the compiler version used, see: http://lists.debian.org/debian-devel/2010/01/msg00230.html The full build log can be found at: http://people.debian.org/~lucas/logs/2010/01/08b/fauhdlc_20091119-1_lsid64b.buildlog The last lines of the build log are cwat the end of this report. The reason of the build failure is likely in the package (compiler or linker message found in the build log), if this turns out as a gcc bug, please reassign to the gcc-4.5 package. If the build ends with a message "confused by earlier errors, bailing out", please ignore it for now; these compiler errors are filed separately. [...] g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare -Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast -U_FORTIFY_SOURCE -Werror -DPACKAGE_NAME=\"fauhdlc\" -DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20091119\" -DPACKAGE_STRING=\"fauhdlc\ 20091119\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20091119\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I. -g -O2 -MT RegisterBuiltins.o -MD -MP -MF .deps/RegisterBuiltins.Tpo -c -o RegisterBuiltins.o `test -f 'frontend/misc/RegisterBuiltins.cpp' || echo './'`frontend/misc/RegisterBuiltins.cpp g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare -Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast -U_FORTIFY_SOURCE -Werror -DPACKAGE_NAME=\"fauhdlc\" -DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20091119\" -DPACKAGE_STRING=\"fauhdlc\ 20091119\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20091119\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I. -g -O2 -MT RangeSet.o -MD -MP -MF .deps/RangeSet.Tpo -c -o RangeSet.o `test -f 'frontend/misc/RangeSet.cpp' || echo './'`frontend/misc/RangeSet.cpp mv -f .deps/ValDeclaration.Tpo .deps/ValDeclaration.Po mv -f .deps/Driver.Tpo .deps/Driver.Po g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare -Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast -U_FORTIFY_SOURCE -Werror -DPACKAGE_NAME=\"fauhdlc\" -DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20091119\" -DPACKAGE_STRING=\"fauhdlc\ 20091119\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20091119\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I. -g -O2 -MT ErrorRegistry.o -MD -MP -MF .deps/ErrorRegistry.Tpo -c -o ErrorRegistry.o `test -f 'frontend/reporting/ErrorRegistry.cpp' || echo './'`frontend/reporting/ErrorRegistry.cpp g++ -Wall -Wextra -Wendif-labels -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-aliasing -Wsign-compare -Wconversion -Wwrite-strings -Wno-unused-parameter -Wold-style-cast -U_FORTIFY_SOURCE -Werror -DPACKAGE_NAME=\"fauhdlc\" -DPACKAGE_TARNAME=\"fauhdlc\" -DPACKAGE_VERSION=\"20091119\" -DPACKAGE_STRING=\"fauhdlc\ 20091119\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"fauhdlc\" -DVERSION=\"20091119\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_GC_GC_CPP_H=1 -I. -g -O2 -MT C
Bug#534193: marked as done (libstdc++6: calling erase() on a new empty string will cause a helgrind error report)
Your message dated Tue, 22 Jun 2010 14:33:27 +0200 with message-id <4c20ad97.5080...@debian.org> and subject line Re: Bug#534193: libstdc++6: calling erase() on a new empty string will cause a helgrind error report has caused the Debian Bug report #534193, regarding libstdc++6: calling erase() on a new empty string will cause a helgrind error 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 your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++6 Version: 4.3.2-1.1 Severity: important http://etbe.coker.com.au/2009/06/22/valgrindhelgrind-and-stl-string http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40518 The above GCC bug report which was created by Jonathan Wakely after reading my blog concerns a case where calling empty() on an empty string will be regarded as not being thread-safe by helgrind. I am not sure if this is a real problem (IE something that can corrupt memory) or whether it's a cosmetic error (something that just causes helgrind warnings). Due to this being the main error that helgrind flags on a program that later has an assertion from free() I suspect that it may actually corrupt memory. But if however it happens to not corrupt memory I still think that it is important enough to justify an update to Lenny to fix this. Allowing debugging tools such as helgrind to work to their maximum potential is quite important to improve the overall quality of the code. I have reproduced this bug in version 4.3.3-12 in Unstable. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages libstdc++6 depends on: ii gcc-4.3-base 4.3.2-1.1 The GNU Compiler Collection (base ii libc62.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1.1 GCC support library libstdc++6 recommends no packages. libstdc++6 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 4.4.4-1 On 22.06.2009 13:59, Russell Coker wrote: Package: libstdc++6 Version: 4.3.2-1.1 Severity: important http://etbe.coker.com.au/2009/06/22/valgrindhelgrind-and-stl-string http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40518 The above GCC bug report which was created by Jonathan Wakely after reading my blog concerns a case where calling empty() on an empty string will be regarded as not being thread-safe by helgrind. I am not sure if this is a real problem (IE something that can corrupt memory) or whether it's a cosmetic error (something that just causes helgrind warnings). Due to this being the main error that helgrind flags on a program that later has an assertion from free() I suspect that it may actually corrupt memory. But if however it happens to not corrupt memory I still think that it is important enough to justify an update to Lenny to fix this. Allowing debugging tools such as helgrind to work to their maximum potential is quite important to improve the overall quality of the code. --- End Message ---
Bug#577961: marked as done (libstdc++6-4.5-dev: Using some part of the STL increase the linkage requirement)
Your message dated Tue, 22 Jun 2010 14:49:01 +0200
with message-id <4c20b13d.3050...@debian.org>
and subject line Re: Bug#577961: libstdc++6-4.5-dev: Using some part of the STL
increase the linkage requirement
has caused the Debian Bug report #577961,
regarding libstdc++6-4.5-dev: Using some part of the STL increase the linkage
requirement
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 your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
577961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6-4.5-dev
Version: 4.5.0-1
Severity: normal
Tags: experimental
Hi,
I'm not sure if this bug behave to libstdc++6-4.5-dev or g++-4.5 or if this
is really a bug.
Here is what I observed: when
* a non-threaded application uses some part of the STL (such as )
and
* the application links to a library itself linked to libpthread
and
* the linker is g++-4.5 (not g++-4.4 or previous)
then
the application itself must be linked with libpthread.
Example:
vdanj...@eyak:/tmp/test$ cat Makefile
CXXLD=$(CXX)
CXXFLAGS=-Wall -fPIC -std=gnu++0x
CPPFLAGS=-I.
all: mymain2 mymain libkapi.so.0
mymain: mymain.o libkapi.so
$(CXXLD) -o $@ $(CXXFLAGS) mymain.o -L. -lkapi
mymain2: mymain.o
$(CXXLD) -o $@ $(CXXFLAGS) mymain.o
libkapi.so: libkapi.so.0
ln -fs $...@.0 $@
kapi.cc:
touch $@
kapi.o: kapi.cc
libkapi.so.0: kapi.o
$(CXXLD) $(CXXFLAGS) -shared -Wl,-soname -Wl,$@ -o $@ $^ -pthread
clean:
$(RM) *.o libkapi.so.0 mymain kapi.cc libkapi.so mymain2
# mymain.cc is the example from
http://www.cplusplus.com/reference/std/memory/uninitialized_copy/
vdanj...@eyak:/tmp/test$ cat mymain.cc
#include
#include
#include
using namespace std;
int main () {
string numbers[] ={"one","two","three"};
// get block of uninitialized memory:
pair result = get_temporary_buffer(3);
if (result.second>0) {
uninitialized_copy ( numbers, numbers+result.second, result.first );
for (int i=0; i (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On 15.04.2010 17:04, Vincent Danjean wrote:
I'm not sure if this bug behave to libstdc++6-4.5-dev or g++-4.5 or if this
is really a bug.
Here is what I observed: when
* a non-threaded application uses some part of the STL (such as)
and
* the application links to a library itself linked to libpthread
and
* the linker is g++-4.5 (not g++-4.4 or previous)
then
the application itself must be linked with libpthread.
I can't reproduce this with current unstable and current g++-4.5 from
experimental. Please reopen if appropriate.
--- End Message ---
Bug#578831: link failure with LTO: “invalid DSO for symbol `pthread_cancel@@GLIBC_2.0' definition”
On 28.04.2010 10:37, Vincent Danjean wrote: On 27/04/2010 01:26, Matthias Klose wrote: On 23.04.2010 10:22, Steinar H. Gunderson wrote: On Fri, Apr 23, 2010 at 08:41:53AM +0200, Vincent Danjean wrote: Please, look at #577961. It seems to me that this is the same bug (and now, I think the bug belong to gcc-4.5) OK, adding -lpthread makes the error go away. please make sure that *all* flags (except preprocessor flags) passed to cc1 are also passed to lto1. For common build systems, this does mean passing $(CFLAGS) to the link command. I do not know for #578831 but, for #577961 the application must not be required to link to -lpthread (and lto1 is not used). please recheck with the current g++-4.5 in experimental. -lpthread shouldn't be used directly, but pass -pthread to both CXXFLAGS and LDFLAGS. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c20b244.5050...@debian.org
Processed: forwarded gcc report
Processing commands for cont...@bugs.debian.org: > forwarded 577458 http://gcc.gnu.org/PR44630 Bug #577458 [libstdc++6-4.5-dev] libstdc++6-4.5-dev: profiler_trace.h defines functions __max and __min which causes portability problems Set Bug forwarded-to-address to 'http://gcc.gnu.org/PR44630'. > tag 577458 + upstream Bug #577458 [libstdc++6-4.5-dev] libstdc++6-4.5-dev: profiler_trace.h defines functions __max and __min which causes portability problems Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 577458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12772114322240.transcr...@bugs.debian.org
Bug#577961: libstdc++6-4.5-dev: Using some part of the STL increase the linkage requirement
fixed 577961 4.5.0-6 On 22/06/2010 14:49, Matthias Klose wrote: > I can't reproduce this with current unstable and current g++-4.5 from > experimental. Please reopen if appropriate. I just checked and can confirm that the current experimental version is ok. Adding this info to the BTS. Regards, Vincent -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11ENSIMAG - antenne de Montbonnot Fax:+33 4 76 61 20 99ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c20bb6f.7090...@debian.org
Processed (with 5 errors): Re: Bug#577961: libstdc++6-4.5-dev: Using some part of the STL increase the linkage requirement
Processing commands for cont...@bugs.debian.org:
> fixed 577961 4.5.0-6
Bug #577961 {Done: Matthias Klose } [libstdc++6-4.5-dev]
libstdc++6-4.5-dev: Using some part of the STL increase the linkage requirement
Bug Marked as fixed in versions gcc-4.5/4.5.0-6.
> On 22/06/2010 14:49, Matthias Klose wrote:
Unknown command or malformed arguments to command.
> > I can't reproduce this with current unstable and current g++-4.5 from
Unknown command or malformed arguments to command.
> > experimental. Please reopen if appropriate.
Unknown command or malformed arguments to command.
> I just checked and can confirm that the current experimental version
Unknown command or malformed arguments to command.
> is ok. Adding this info to the BTS.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
577961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.127721356019470.transcr...@bugs.debian.org
Processed: Re: Bug#581571: [sparc] long long to double conversion error
Processing commands for cont...@bugs.debian.org: > forwarded 581571 http://gcc.gnu.org/PR44631 Bug #581571 [gcc-4.4] [sparc] long long to double conversion error Set Bug forwarded-to-address to 'http://gcc.gnu.org/PR44631'. > tag 581571 + upstream Bug #581571 [gcc-4.4] [sparc] long long to double conversion error Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 581571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127721353019288.transcr...@bugs.debian.org
Processed: Re: Bug#585925: g++-4.4: bogus results of complex division
Processing commands for cont...@bugs.debian.org: > forwarded 585925 http://gcc.gnu.org/44632 Bug #585925 [g++-4.4] g++-4.4: bogus results of complex division Set Bug forwarded-to-address to 'http://gcc.gnu.org/44632'. > tag 585925 + upstream Bug #585925 [g++-4.4] g++-4.4: bogus results of complex division Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 585925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127721521530963.transcr...@bugs.debian.org
Bug#567695: smaller test case enclosed
On 23.02.2010 23:47, Falk Hueffner wrote: On Thu, Feb 04, 2010 at 09:55:42AM -0500, Camm Maguire wrote: This test program will segfault at -O2 on the affected machines: Can you please repost the attachment? It is not retrievable from the BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567695 ... the attachments are retrievable, but don't build -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c20c7d1.1090...@debian.org
Processed: forwarded gcc report
Processing commands for cont...@bugs.debian.org: > forwarded 566242 http://gcc.gnu.org/PR44634 Bug #566242 [gcc-4.4] gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954 Set Bug forwarded-to-address to 'http://gcc.gnu.org/PR44634'. > tag 566242 + upstream Bug #566242 [gcc-4.4] gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 566242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127721786425091.transcr...@bugs.debian.org
Bug#566242: gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954
tag 566242 + wontfix tag 566242 + upstream tag 566242 + fixed-upstream fixed in 4.5. won't fix in 4.4. Use -mcpu=v9 as a workaround for gcc-4.4. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c20cf3d.9040...@debian.org
Processed (with 1 errors): Re: Bug#566242: gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954
Processing commands for cont...@bugs.debian.org: > tag 566242 + wontfix Bug #566242 [gcc-4.4] gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954 Added tag(s) wontfix. > tag 566242 + upstream Bug #566242 [gcc-4.4] gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954 Ignoring request to alter tags of bug #566242 to the same tags previously set > tag 566242 + fixed-upstream Bug #566242 [gcc-4.4] gcc-4.4: ICE when building polybori 0.5~rc1-2.1 on sparc: in change_address_1, at emit-rtl.c:1954 Added tag(s) fixed-upstream. > fixed in 4.5. won't fix in 4.4. Use -mcpu=v9 as a workaround for gcc-4.4. Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 566242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.127721863030883.transcr...@bugs.debian.org
Processed: forwarded gcc report
Processing commands for cont...@bugs.debian.org: > forwarded 582085 http://gcc.gnu.org/44636 Bug #582085 [gfortran-4.4] gfortran-4.4 regression: the -i4 option is not supported anymore Set Bug forwarded-to-address to 'http://gcc.gnu.org/44636'. > tags 582085 + upstream Bug #582085 [gfortran-4.4] gfortran-4.4 regression: the -i4 option is not supported anymore Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 582085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12772218654012.transcr...@bugs.debian.org
Results for 4.4.4 (Debian 4.4.4-6) testsuite on x86_64-pc-linux-gnu
LAST_UPDATED: Obtained from SVN: tags/gcc_4_4_4_release revision 158895 Target: x86_64-linux-gnu gcc version 4.4.4 (Debian 4.4.4-6) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes19943 # of expected failures 157 # of unsupported tests 253 Running target unix/-fstack-protector === g++ Summary for unix/-fstack-protector === # of expected passes19943 # of expected failures 157 # of unsupported tests 253 Running target unix/-m32 === g++ Summary for unix/-m32 === # of expected passes20262 # of expected failures 157 # of unsupported tests 101 === g++ Summary === # of expected passes60148 # of expected failures 471 # of unsupported tests 607 /scratch/packages/gcc/4.4/gcc-4.4-4.4.4/build/gcc/testsuite/g++/../../g++ version 4.4.4 (Debian 4.4.4-6) === gcc tests === Running target unix FAIL: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/bb-reorg.c execution,-fprofile-use -D_PROFILE_USE FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution,-fprofile-use -D_PROFILE_USE === gcc Summary for unix === # of expected passes57922 # of unexpected failures2 # of expected failures 192 # of unresolved testcases 2 # of unsupported tests 735 Running target unix/-fstack-protector WARNING: program timed out. FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors) FAIL: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/bb-reorg.c execution,-fprofile-use -D_PROFILE_USE FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution,-fprofile-use -D_PROFILE_USE === gcc Summary for unix/-fstack-protector === # of expected passes57921 # of unexpected failures3 # of expected failures 192 # of unresolved testcases 2 # of unsupported tests 735 Running target unix/-m32 === gcc Summary for unix/-m32 === # of expected passes58282 # of expected failures 193 # of unsupported tests 446 === gcc Summary === # of expected passes174125 # of unexpected failures5 # of expected failures 577 # of unresolved testcases 4 # of unsupported tests 1916 /scratch/packages/gcc/4.4/gcc-4.4-4.4.4/build/gcc/xgcc version 4.4.4 (Debian 4.4.4-6) === gfortran tests === Running target unix === gfortran Summary for unix === # of expected passes30365 # of expected failures 13 # of unsupported tests 44 Running target unix/-fstack-protector === gfortran Summary for unix/-fstack-protector === # of expected passes30365 # of expected failures 13 # of unsupported tests 44 Running target unix/-m32 === gfortran Summary for unix/-m32 === # of expected passes30236 # of expected failures 13 # of unsupported tests 105 === gfortran Summary === # of expected passes90966 # of expected failures 39 # of unsupported tests 193 /scratch/packages/gcc/4.4/gcc-4.4-4.4.4/build/gcc/testsuite/gfortran/../../gfortran version 4.4.4 (Debian 4.4.4-6) === obj-c++ tests === Running target unix XPASS: obj-c++.dg/comp-types-10.mm (test for excess errors) UNRESOLVED: obj-c++.dg/lookup-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-9.mm compilation failed to produce executable === obj-c++ Summary for unix === # of expected passes425 # of unexpected successes 1 # of expected failures 20 # of unresolved testcases 3 # of unsupported tests 13 Running target unix/-fstack-protector XPASS: obj-c++.dg/comp-types-10.mm (test for excess errors) UNRESOLVED: obj-c++.dg/lookup-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-2.mm compilation failed to produce executable UNRESOLVED: obj-c++.dg/try-catch-9.mm compilation failed to produce executable === obj-c++ Summary for unix/-fstack-protector === # of expected passes425 # of unexpected successes 1 # of expected failures 20 # of unresolved testcases 3 # of unsupported tests 13 Running target unix/-m32 XPASS: obj-c++.dg/comp-types-10.mm (test for excess errors) UNR
Results for 4.5.1 20100621 (prerelease) (Debian 4.5.0-7) testsuite on x86_64-pc-linux-gnu
LAST_UPDATED: Obtained from SVN: tags/gcc_4_5_0_release revision 158339 Target: x86_64-linux-gnu gcc version 4.5.1 20100621 (prerelease) (Debian 4.5.0-7) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes22826 # of expected failures 151 # of unsupported tests 303 Running target unix/-fstack-protector === g++ Summary for unix/-fstack-protector === # of expected passes22826 # of expected failures 151 # of unsupported tests 303 Running target unix/-m32 === g++ Summary for unix/-m32 === # of expected passes23223 # of expected failures 151 # of unsupported tests 113 === g++ Summary === # of expected passes68875 # of expected failures 453 # of unsupported tests 719 /scratch/packages/gcc/4.5/gcc-4.5-4.5.0/build/gcc/testsuite/g++/../../g++ version 4.5.1 20100621 (prerelease) (Debian 4.5.0-7) === gcc tests === Running target unix FAIL: gcc.dg/pr34668-1.c (internal compiler error) FAIL: gcc.dg/pr34668-1.c (test for excess errors) XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O1 execution test XPASS: gcc.dg/guality/example.c -O2 execution test XPASS: gcc.dg/guality/example.c -O2 -flto execution test XPASS: gcc.dg/guality/example.c -O2 -fwhopr execution test XPASS: gcc.dg/guality/guality.c -O0 execution test XPASS: gcc.dg/guality/guality.c -O1 execution test XPASS: gcc.dg/guality/guality.c -O2 execution test XPASS: gcc.dg/guality/guality.c -O3 -fomit-frame-pointer execution test XPASS: gcc.dg/guality/guality.c -O3 -g execution test XPASS: gcc.dg/guality/guality.c -Os execution test XPASS: gcc.dg/guality/guality.c -O2 -flto execution test XPASS: gcc.dg/guality/guality.c -O2 -fwhopr execution test XPASS: gcc.dg/guality/pr41353-1.c -O0 line 28 j == 28 + 37 XPASS: gcc.dg/guality/pr41353-1.c -O1 line 28 j == 28 + 37 XPASS: gcc.dg/guality/pr41353-1.c -O2 line 28 j == 28 + 37 XPASS: gcc.dg/guality/pr41353-1.c -O3 -fomit-frame-pointer line 28 j == 28 + 37 XPASS: gcc.dg/guality/pr41353-1.c -O3 -g line 28 j == 28 + 37 XPASS: gcc.dg/guality/pr41353-1.c -Os line 28 j == 28 + 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -flto line 28 i == 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -flto line 28 i1 == 2 * 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -flto line 28 i2 == 3 * 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -fwhopr line 28 i == 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -fwhopr line 28 i1 == 2 * 37 FAIL: gcc.dg/guality/pr41353-1.c -O2 -fwhopr line 28 i2 == 3 * 37 XPASS: gcc.dg/guality/pr41447-1.c -O0 execution test XPASS: gcc.dg/guality/pr41616-1.c -O0 execution test XPASS: gcc.dg/guality/pr41616-1.c -O1 execution test XPASS: gcc.dg/guality/pr41616-1.c -O2 execution test XPASS: gcc.dg/guality/pr41616-1.c -Os execution test XPASS: gcc.dg/guality/pr41616-1.c -O2 -flto execution test XPASS: gcc.dg/guality/pr41616-1.c -O2 -fwhopr execution test FAIL: gcc.dg/guality/vla-1.c -O0 line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O0 line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O1 line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O1 line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O2 line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O2 line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O3 -fomit-frame-pointer line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O3 -fomit-frame-pointer line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O3 -g line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O3 -g line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -Os line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -Os line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O2 -flto line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O2 -flto line 24 sizeof (a) == 17 * sizeof (short) FAIL: gcc.dg/guality/vla-1.c -O2 -fwhopr line 17 sizeof (a) == 6 FAIL: gcc.dg/guality/vla-1.c -O2 -fwhopr line 24 sizeof (a) == 17 * sizeof (short) === gcc Summary for unix === # of expected passes72641 # of unexpected failures24 # of unexpected successes 26 # of expected failures 199 # of unsupported tests 964 Running target unix/-fstack-protector FAIL: gcc.dg/pr34668-1.c (internal compiler error) FAIL: gcc.dg/pr34668-1.c (test for excess errors) XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -O1 execution test XPASS: gcc.dg/guality/example.c -O2 execution test XPASS: gcc.dg/guality/example.c -O2 -flto execution test XPASS: gcc.dg/guality/example.c -O2 -fwhopr execution test XPASS: gcc.
Results for 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian 20100621-1) testsuite on i486-pc-linux-gnu
LAST_UPDATED: Mon Jun 21 08:53:49 UTC 2010 (revision 161065)
Target: i486-linux-gnu
gcc version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian
20100621-1)
=== acats tests ===
FAIL: c94008d
=== acats Summary ===
# of expected passes2320
# of unexpected failures1
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o execute -O2
-fwhopr
=== g++ Summary for unix ===
# of expected passes23923
# of unexpected failures1
# of expected failures 148
# of unsupported tests 118
Running target unix/-m64
=== g++ Summary for unix/-m64 ===
# of expected passes24145
# of expected failures 148
# of unsupported tests 321
=== g++ Summary ===
# of expected passes48068
# of unexpected failures1
# of expected failures 296
# of unsupported tests 439
/build/buildd-gcc-snapshot_20100621-1-i386-Me6kjJ/gcc-snapshot-20100621/build/gcc/testsuite/g++/../../g++
version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian
20100621-1)
=== gcc tests ===
Running target unix
FAIL: gcc.c-torture/execute/frame-address.c execution, -O2
FAIL: gcc.c-torture/execute/frame-address.c execution, -O3 -g
FAIL: gcc.c-torture/execute/frame-address.c execution, -Os
FAIL: gcc.c-torture/execute/frame-address.c execution, -O2 -flto
FAIL: gcc.c-torture/execute/frame-address.c execution, -O2 -fwhopr
FAIL: gcc.dg/cproj-fails-with-broken-glibc.c execution test
FAIL: gcc.dg/pr34668-1.c (internal compiler error)
FAIL: gcc.dg/pr34668-1.c (test for excess errors)
XPASS: gcc.dg/tree-ssa/20040204-1.c scan-tree-dump-times optimized "link_error" 0
=== gcc Summary for unix ===
# of expected passes73064
# of unexpected failures8
# of unexpected successes 1
# of expected failures 179
# of unsupported tests 598
Running target unix/-m64
FAIL: gcc.dg/cproj-fails-with-broken-glibc.c execution test
FAIL: gcc.dg/pr34668-1.c (internal compiler error)
FAIL: gcc.dg/pr34668-1.c (test for excess errors)
XPASS: gcc.dg/tree-ssa/20040204-1.c scan-tree-dump-times optimized "link_error" 0
=== gcc Summary for unix/-m64 ===
# of expected passes73179
# of unexpected failures3
# of unexpected successes 1
# of expected failures 178
# of unsupported tests 983
=== gcc Summary ===
# of expected passes146243
# of unexpected failures11
# of unexpected successes 2
# of expected failures 357
# of unsupported tests 1581
/build/buildd-gcc-snapshot_20100621-1-i386-Me6kjJ/gcc-snapshot-20100621/build/gcc/xgcc
version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian
20100621-1)
=== gfortran tests ===
Running target unix
=== gfortran Summary for unix ===
# of expected passes34738
# of expected failures 33
# of unsupported tests 145
Running target unix/-m64
=== gfortran Summary for unix/-m64 ===
# of expected passes34897
# of expected failures 33
# of unsupported tests 71
=== gfortran Summary ===
# of expected passes69635
# of expected failures 66
# of unsupported tests 216
/build/buildd-gcc-snapshot_20100621-1-i386-Me6kjJ/gcc-snapshot-20100621/build/gcc/testsuite/gfortran/../../gfortran
version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian
20100621-1)
=== gnat tests ===
Running target unix
=== gnat Summary for unix ===
# of expected passes805
# of expected failures 10
# of unsupported tests 1
Running target unix/-m64
UNRESOLVED: gnat.dg/abstract_with_anonymous_result.adb compilation failed to
produce executable
UNRESOLVED: gnat.dg/access4.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/access_discr2.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/access_test.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/addr2.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/address_conversion.adb compilation failed to produce
executable
UNRESOLVED: gnat.dg/aggr1.adb compilation failed to produce executable
FAIL: gnat.dg/aggr12.adb scan-tree-dump-not original "{.i1=0, .i2=2}": dump
file does not exist
FAIL: gnat.dg/aggr13.adb scan-tree-dump-not gimple "= {}": dump file does not
exist
UNRESOLVED: gnat.dg/aggr14.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/aggr3.adb compilation failed to produce executable
UNRESOLVED: gnat.dg/aliased_prefix_accessibility.adb compilation failed to
produce executable
FAIL: gn
Results for 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian 20100621-1) testsuite on powerpc-unknown-linux-gnu
LAST_UPDATED: Mon Jun 21 08:53:49 UTC 2010 (revision 161065) Target: powerpc-linux-gnu gcc version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian 20100621-1) === acats tests === === acats Summary === # of expected passes2321 # of unexpected failures0 Native configuration is powerpc-unknown-linux-gnu === g++ tests === Running target unix WARNING: program timed out. FAIL: g++.dg/bprob/g++-bprob-2.C execution,-Os -fprofile-use FAIL: g++.dg/ext/altivec-17.C (test for errors, line 15) FAIL: g++.dg/ext/altivec-17.C (test for excess errors) FAIL: g++.dg/ext/altivec-2.C (test for excess errors) FAIL: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o execute -O2 -fwhopr === g++ Summary for unix === # of expected passes23226 # of unexpected failures5 # of expected failures 148 # of unsupported tests 159 Running target unix/-m64 FAIL: g++.dg/ext/altivec-17.C (test for errors, line 15) FAIL: g++.dg/ext/altivec-17.C (test for excess errors) FAIL: g++.dg/ext/altivec-2.C (test for excess errors) FAIL: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o execute -O2 -fwhopr === g++ Summary for unix/-m64 === # of expected passes23838 # of unexpected failures4 # of expected failures 148 # of unsupported tests 157 === g++ Summary === # of expected passes47064 # of unexpected failures9 # of expected failures 296 # of unsupported tests 316 /build/buildd-gcc-snapshot_20100621-1-powerpc-CVl0jk/gcc-snapshot-20100621/build/gcc/testsuite/g++/../../g++ version 4.6.0 20100621 (experimental) [trunk revision 161065] (Debian 20100621-1) === gcc tests === Running target unix FAIL: gcc.c-torture/execute/frame-address.c execution, -O2 FAIL: gcc.c-torture/execute/frame-address.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/frame-address.c execution, -O3 -g FAIL: gcc.c-torture/execute/frame-address.c execution, -Os FAIL: gcc.c-torture/execute/frame-address.c execution, -O2 -flto FAIL: gcc.c-torture/execute/frame-address.c execution, -O2 -fwhopr FAIL: gcc.dg/and-1.c scan-assembler-not nand FAIL: gcc.dg/cproj-fails-with-broken-glibc.c execution test FAIL: gcc.dg/pr34668-1.c (internal compiler error) FAIL: gcc.dg/pr34668-1.c (test for excess errors) FAIL: gcc.dg/sms-2.c scan-rtl-dump-times sms "SMS succeeded" 1 FAIL: gcc.dg/sms-4.c scan-rtl-dump-times sms "SMS succeeded" 1 FAIL: gcc.dg/sms-6.c scan-rtl-dump-times sms "SMS succeeded" 3 FAIL: gcc.dg/sms-7.c scan-rtl-dump-times sms "SMS succeeded" 3 FAIL: gcc.dg/sms-8.c scan-rtl-dump-times sms "SMS succeeded" 1 FAIL: gcc.dg/uninit-pred-9_b.c bogus warning (test for bogus messages, line 24) FAIL: gcc.dg/lto/20100518 c_lto_20100518_0.o assemble, -O0 -fwhopr UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o link -O0 -fwhopr UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o execute -O0 -fwhopr FAIL: gcc.dg/lto/20100518 c_lto_20100518_0.o assemble, -O2 -fwhopr UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o link -O2 -fwhopr UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o execute -O2 -fwhopr FAIL: gcc.dg/lto/20100518 c_lto_20100518_0.o assemble, -O0 -flto UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o link -O0 -flto UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o execute -O0 -flto FAIL: gcc.dg/lto/20100518 c_lto_20100518_0.o assemble, -O2 -flto UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o link -O2 -flto UNRESOLVED: gcc.dg/lto/20100518 c_lto_20100518_0.o-c_lto_20100518_0.o execute -O2 -flto FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _ans" 0 FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _T2" 0 FAIL: gcc.dg/tree-ssa/vrp47.c scan-tree-dump-times vrp1 "[xy][^ ]* !=" 0 FAIL: gcc.dg/tree-ssa/vrp47.c scan-tree-dump-times dom1 "x[^ ]* & y" 1 FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-31d.c scan-tree-dump-times vect "vectorization not profitable" 1 FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-68d.c scan-tree-dump-times vect "vectorization not profitable" 1 FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-76a.c scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c scan-tree-dump-times vect "vectorization not profitable" 1 FAIL: gcc.dg/vect/pr35821-altivec.c scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/vect-109.c scan-tree-dump-times vect "vectorized 1 loops" 2 FAIL: gcc.target/powerpc/405-dlmzb-strlen-1.c scan-assembler dlmzb. FAIL: gcc.target/powerpc/440-dlmzb-strlen-1.c scan-assembler dlmzb. FAIL: gcc.target/powerpc/altivec-volatile.c (test for warnings, line
Bug#578831: link failure with LTO: “invalid DSO for symbol `pthread_cancel@@GLIBC_2.0' definition”
On Tue, Jun 22, 2010 at 02:53:24PM +0200, Matthias Klose wrote: > please recheck with the current g++-4.5 in experimental. -lpthread > shouldn't be used directly, but pass -pthread to both CXXFLAGS and > LDFLAGS. Pretty much no change. With CXXFLAGS including -pthread and LDFLAGS including -pthread -flto -fwhole-program: script/script.a(curve.o): In function `_ZN6script5Curve13make_tangentsEv': curve.cpp:(.text._ZN6script5Curve13make_tangentsEv+0x3f2): undefined reference to `_ZN6script6engine13get_num_paramENS_5Curve8knottypeE' script/script.a(curve.o): In function `_ZN6script5Curve9get_valueEfPf': curve.cpp:(.text._ZN6script5Curve9get_valueEfPf+0x226): undefined reference to `_ZN6script6engine7targetsE' curve.cpp:(.text._ZN6script5Curve9get_valueEfPf+0x236): undefined reference to `_ZN6script6engine8texturesE' curve.cpp:(.text._ZN6script5Curve9get_valueEfPf+0x262): undefined reference to `_ZN6script6engine6meshesE' curve.cpp:(.text._ZN6script5Curve9get_valueEfPf+0x28b): undefined reference to `_ZN6script6engine9materialsE' curve.cpp:(.text._ZN6script5Curve9get_valueEfPf+0x2a1): undefined reference to `_ZN6script6engine13get_num_paramENS_5Curve8knottypeE' collect2: ld returned 1 exit status make: *** [intro] Error 1 Without -fwhole-program in LDFLAGS it links, as before. With -frepo in the mix, it's chaos as usual, with tons and tons of messages like script/parser.o: In function `_ZNSt8_Rb_treeISsSt4pairIKSsN6script6parser4meshEESt10_Select1stIS5_ESt4lessISsESaIS5_EE4findERS1_.clone.30': parser.cpp:(.text._ZNSt8_Rb_treeISsSt4pairIKSsN6script6parser4meshEESt10_Select1stIS5_ESt4lessISsESaIS5_EE4findERS1_.clone.30+0x38): undefined reference to `bool std::operator< , std::allocator >(std::basic_string, std::allocator > const&, std::basic_string, std::allocator > const&)' and other mising templates. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100622174315.ga3...@uio.no
Bug#585730: please build insighttoolkit for ia64 on mundy.debian.org
On Sun, Jun 13, 2010 at 09:19:43PM -0500, Steve M. Robbins wrote: > Hi, > > I'd like to request that mundy.debian.org try building insighttoolkit > version 3.18.0-3. Mundy succesfully built the previous three versions, > but the latest build was executed on caballero and failed. I'd like > to try with mundy to see whether there's a machine-specific problem > with caballero (as happened with kfreebsd-amd64 [1]). > > gb insighttoolkit_3.18.0-3 . ia64 . -m 'Rebuild on mundy.' I've given it back, but I can't select the buildd that will try it. Kurt -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100622184753.gc15...@roeckx.be
Bug#585730: please build insighttoolkit for ia64 on mundy.debian.org
On Sun, Jun 13, 2010 at 09:19:43PM -0500, Steve M. Robbins wrote: > Hi, > > gb insighttoolkit_3.18.0-3 . ia64 . -m 'Rebuild on mundy.' This was probably #576198, it's atleast a simular error message. Kurt -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100622185129.ge15...@roeckx.be
Bug#582085: marked as done (gfortran-4.4 regression: the -i4 option is not supported anymore)
Your message dated Wed, 23 Jun 2010 01:06:08 +0200 with message-id <4c2141e0.5070...@debian.org> and subject line Re: Bug#582085: gfortran-4.4 regression: the -i4 option is not supported anymore has caused the Debian Bug report #582085, regarding gfortran-4.4 regression: the -i4 option is not supported anymore 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 your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 582085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gfortran-4.4 Version: 4.4.4-1 Severity: normal Hello, gfortran-4.4 does not support anymore the -i4 option, while gfortran-4.3 does. This is necessary for me to compile gildas (see http://www.iram.fr/~gildas/dist/index.html). Is there any specific reason why support for this flag was dropped from 4.4 ? Cheers, Vincent -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gfortran-4.4 depends on: ii gcc-4.4 4.4.4-1The GNU C compiler ii gcc-4.4-base 4.4.4-1The GNU Compiler Collection (base ii libc6 2.10.2-8 Embedded GNU C Library: Shared lib ii libc6-dev 2.10.2-8 Embedded GNU C Library: Developmen ii libgfortran3 4.4.4-1Runtime library for GNU Fortran ap ii libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library ii libmpfr1ldbl 2.4.2-3multiple precision floating-point gfortran-4.4 recommends no packages. Versions of packages gfortran-4.4 suggests: pn gfortran-4.4-doc (no description available) pn gfortran-4.4-multilib (no description available) pn libgfortran3-dbg (no description available) -- no debconf information --- End Message --- --- Begin Message --- closing (invalid). -i4 was never supported. See the upstream report for comments. On 18.05.2010 10:56, Vincent Fourmond wrote: On Tue, May 18, 2010 at 10:44 AM, Matthias Klose wrote: On 18.05.2010 10:19, Vincent Fourmond wrote: Package: gfortran-4.4 Version: 4.4.4-1 Severity: normal Hello, gfortran-4.4 does not support anymore the -i4 option, while gfortran-4.3 does. This is necessary for me to compile gildas (see http://www.iram.fr/~gildas/dist/index.html). Is there any specific reason why support for this flag was dropped from 4.4 ? didn't check. is this seen with 4.5/snapshot as well? Yes: 10:55 fourm...@zorglub ~/Prog/Soas/source gfortran-4.3 -c -i4 soas_misc.f 10:55 fourm...@zorglub ~/Prog/Soas/source gfortran-4.4 -c -i4 soas_misc.f f951: error: unrecognized command line option "-i4" 10:55 fourm...@zorglub ~/Prog/Soas/source gfortran-4.5 -c -i4 soas_misc.f f951: error: unrecognized command line option "-i4" Cheers, Vincent (although it seems it isn't the reason why my crash happened in the first place) --- End Message ---
