Re: GCC (I think) Internal compiler error
David Mandala writes: > When attempting to build php 4.1.1 on my netwinder I get the following > error messages, which seem to be a gcc error, not sure where to go from > here. AFAIK php4 doesn't build with gcc-2.95.x. Try using gcc-3.0 (if you can find a version, which you can install ..., because gcc-3.0.[234] currently does not build on arm)
out of date python-related packages on arm
Please have a look at the following packages, they have been built, but cannot be found in the unstable archives. These packages are libraries, which are needed by other packages. egenix-mx-base ood arm built, not uploaded python-popy ood arm needs egenix-mx-base be built python-pgsql ood arm needs egenix-mx-base be built python-ldap ood arm built, not uploaded python-mysqldb ood arm built, not uploaded quantlib-python ood arm no build attempts
help needed with regression from g++-2.95 to g++-3.2 on arm
As this report seems to be an regression from g++-2.95, I would like to forward this one ... Please could someone attach the preprocessed source to the report? See http://bugs.debian.org/168086 Thanks, Matthias PS: And if gcc-snapshot is built for arm, test if it's fixed ...
binutils build failures on arm
Package: binutils Version: 2.13.90.0.16 and up. Severity: important The last binutils version that build for arm was 2.13.90.0.14. The build failure is due to an ICE in gcc-3.2 while building the multiarch version. Building with gcc-2.95 works fine. However I see the following testsuite differences (attached). At least that's better than the gcc-3.2 based builds (19 unexpected failures in ld). See http://buildd.debian.org/fetch.php?&pkg=binutils&ver=2.13.90.0.18-1.3&arch=arm&stamp=1048336993&file=log&as=raw What to do: - leave binutils alone? - upload the build done with gcc-2.95 and glibc-2.2 (in stable)? - upload the build done with gcc-2.95 and glibc-2.3 (in unstable)? - disable building the multiarch package and upload the package using gcc-3.2? The build done with gcc-2.95 and glibc-2.2 shows no failures, but untested cases. It seems to be the safest choice to go. --- gcc-2.95-glibc-2.2/test-summary Sun Mar 23 14:13:31 2003 +++ gcc-2.95-glibc-2.3/test-summary Sun Mar 23 13:38:21 2003 @@ -1,4 +1,4 @@ -Test Run By doko on Sun Mar 23 11:19:20 2003 +Test Run By doko on Sun Mar 23 12:31:31 2003 Native configuration is arm-unknown-linux-gnu === binutils tests === @@ -26,10 +26,10 @@ PASS: objcopy --adjust-section-vma = PASS: strip PASS: strip with saving a symbol -PASS: simple objcopy of executable -PASS: run objcopy of executable -PASS: run stripped executable -PASS: run stripped executable with saving a symbol +UNTESTED: simple objcopy of executable +UNTESTED: run objcopy of executable +UNTESTED: run stripped executable +UNTESTED: run stripped executable with saving a symbol Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/binutils/testsuite/binutils-all/objdump.exp ... PASS: objdump -i PASS: objdump -f @@ -51,9 +51,10 @@ === binutils Summary === -# of expected passes 31 +# of expected passes 27 # of expected failures 1 -Test Run By doko on Sun Mar 23 11:20:03 2003 +# of untested testcases4 +Test Run By doko on Sun Mar 23 12:32:12 2003 Native configuration is arm-unknown-linux-gnu === gas tests === @@ -126,8 +127,12 @@ Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/h8300/h8300-elf.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/h8300/h8300.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/basic/basic.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/basic/basic.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/parse/parse.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/parse/parse.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/reloc/reloc.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/reloc/reloc.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/unsorted/unsorted.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/hppa/unsorted/unsorted.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/i386/i386.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/ia64/ia64.exp ... @@ -175,6 +180,8 @@ Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/basic.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/err.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/sh64/err.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/sh64/err.exp ... +Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/sh64/sh64.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sh/sh64/sh64.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sparc-solaris/addend.exp ... Running /home/doko/binutils/binutils-2.13.90.0.18/build-tree/binutils-2.13.90.0.18/gas/testsuite/gas/sparc-solaris/gas.exp ... @@ -203,7 +210,7 @@ # of expected passes 63 ../as-new Inc. -Test Run By doko on Sun Mar 23 11:20:59 2003 +Test Run By doko on Sun Mar 23 12:33:09 2003 Native configuration is arm-unknown-linux-gnu
Re: what's up with gts?
Philip Blundell writes: > On Fri, 2003-06-20 at 10:24, Marcelo E. Magallon wrote: > > (sid)[EMAIL PROTECTED]:~/gts-0.7.1/src$ gcc -DHAVE_CONFIG_H -I. -I. -I.. > > -I.. -I/usr/include -DG_LOG_DOMAIN=\"Gts\" -O2 -Wall -Wall > > -Werror-implicit-function-declaration -Wstrict-prototypes > > -Wmissing-prototypes -Wmissing-declarations -I/usr/include/glib-1.2 > > -I/usr/lib/glib/include -c predicates.c -MT predicates.lo -MD -MP -MF > > .deps/predicates.TPlo -o predicates.o > > predicates.c: In function `insphereexact': > > predicates.c:2368: internal compiler error: in change_address_1, at > > emit-rtl.c:2017 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See http://gcc.gnu.org/bugs.html> for instructions. > > Okay. Please file a bug so that we don't lose track of this problem, if > there isn't already one open. Please can you recheck on debussy unstable using CC="/home/doko/3.3/gcc-3.3-3.3.1ds0/build/gcc/xgcc -B/home/doko/3.3/gcc-3.3-3.3.1ds0/build/gcc/" Matthias
Re: Latest GCC didn't autobuild on arm
Colin Watson writes: > On Sat, Sep 20, 2003 at 10:06:29PM -0400, Nathanael Nerode wrote: > > It somehow seems not to have installed doxygen, for unknown reasons. > > Hopefully this can be resolved ASAP? ... > > This was a bug in dpkg-buildpackage: it forgot the -B flag to > dpkg-checkbuilddeps, which promptly objected to the lack of > Build-Depends-Indep:. Upgrading dpkg-dev in the autobuilder's chroot > should fix that. the build failed for the last uploads as well (as it did on debussy when started manually). Phil did reschedule the build the last times, which always succeeded, so maybe this could be redone? Matthias
Re: internal compiler error on arm
J.H.M. Dassen (Ray) writes: > On Sun, Feb 22, 2004 at 19:53:26 +0100, Martin Godisch wrote: > > sh.dir.c:641: internal compiler error: in reload_cse_simplify_operands, at > > reload1.c:8353 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See http://gcc.gnu.org/bugs.html> for instructions. > > > What's the right thing to do? > > Follow /usr/share/doc/gcc-3.3/README.Bugs.gz . see #233633. Phil is testing a fix.
Re: (ia64/arm/m68k/unstable): FTBFS: segv in miniperl
This may be a compiler bug. On ia64 the package builds using gcc-3.4 from experimental. I didn't try to build 5.8.3 to see if this was triggered by the new perl version. Maybe it's an alternative to build miniperl with gcc-2.96 on ia64 and gcc-2.95 on arm and m68k?
Bug#270202: qt-x11-free build error on arm-linux
Package: qt-x11-free Version: 3:3.3.3-4 Severity: serious [please don't reassign yet, let's evaluate it first; this is the package that most people would expect to find a report] when building on arm-linux, uic enters an infinite loop building pixmapfunction.h. It's not the first uic invocation in the build. (gdb) run Starting program: /home/matthias/qt/qt-x11-free-3.3.3/bin/uic -L plugins tools/designer/designer/pixmapfunction.ui -o pixmapfunction.h [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 31697)] Program received signal SIGINT, Interrupt. [Switching to Thread 16384 (LWP 31697)] 0x40506024 in mult () from lib/libqt-mt.so.3 the process uses all CPU time, strace doesn't show any output. suspecting a toolchain issue, the following combinations of versions and flags, all reproducing the same results, were tried: - current gcc-3.3(sid), binutils-2.15-2, current glibc (-16), qt with -O2 - current gcc-3.3(sid), binutils-2.15-2, current glibc (-16), qt with -O0 - current gcc-3.3(sid), binutils-2.14.90.0.7-8, current glibc (-16), qt with -O2 - current gcc-3.3(sid), binutils-2.14.90.0.7-8, glibc (-16), qt with -O2 - current gcc-3.3(sid), binutils-2.15-2, current glibc (-16), qt with -O0 - current gcc-3.4(sid), binutils-2.15-2, current glibc (-16), qt with -O2 - current gcc-3.3(sid), binutils-2.15-2, current glibc (-16) rebuilt with current gcc-3.3(sid), binutils-2.15-2 qt with -O2 Currently trying to build with current sarge tools. Matthias
