[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#446857: can't build qgis on arm



Package: gcc-4.2
Version: 4.2.2-2
Severity: grave


See
http://buildd.debian.org/fetch.cgi?pkg=qgis;ver=0.8.1-2;arch=arm;stamp=1192513709

/build/buildd/qgis-0.8.1/src/plugins/grass/qgsgrassedit.cpp: At global scope:
/build/buildd/qgis-0.8.1/src/plugins/grass/qgsgrassedit.cpp:1840: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[3]: *** [src/plugins/grass/CMakeFiles/grassplugin.dir/qgsgrassedit.o] Error 1
make[3]: Leaving directory `/build/buildd/qgis-0.8.1'
make[2]: *** [src/plugins/grass/CMakeFiles/grassplugin.dir/all] Error 2
make[2]: Leaving directory `/build/buildd/qgis-0.8.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/qgis-0.8.1'
make: *** [build-stamp] Error 2

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.2 depends on:
ii  binutils                      2.18-1     The GNU assembler, linker and bina
ii  cpp-4.2                       4.2.2-2    The GNU C preprocessor
ii  gcc-4.2-base                  4.2.2-2    The GNU Compiler Collection (base 
ii  libc6                         2.6.1-5    GNU C Library: Shared libraries
ii  libgcc1                       1:4.2.2-2  GCC support library
ii  libgomp1                      4.2.2-2    GCC OpenMP (GOMP) support library

Versions of packages gcc-4.2 recommends:
ii  libc6-dev                     2.6.1-5    GNU C Library: Development Librari

-- no debconf information




Reply to: