Package: gxemul
Version: 0.4.1-1
Severity: important

gxemul fails to build from source on m68k.

Here are selected excerpts from the buildd log.


| Automatic build of gxemul_0.4.1-1 on spice by sbuild/m68k 85
| Build started at 20060726-0945
| ******************************************************************************

 [...]

| ** Using build dependencies supplied by package:
| Build-Depends: debhelper (>= 4.1.0), libx11-dev

 [...]

| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.3.6-15 
linux-kernel-headers_2.6.17.6-1 gcc-4.1_4.1.1-8 g++-4.1_4.1.1-8 
binutils_2.17-1+b1 libstdc++6-4.1-dev_4.1.1-8 libstdc++6_4.1.1-8

 [...]

| make[2]: Leaving directory `/build/buildd/gxemul-0.4.1/src'
| cc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -fomit-frame-pointer 
-fpeephole -O3  -O2 src/*.o src/cpus/*.o src/debugger/*.o src/devices/*.o 
src/machines/*.o src/promemul/*.o -L/usr/X11R6/lib -lX11 -lm  -o gxemul
| src/cpu.o: In function `cpu_init':
| /build/buildd/gxemul-0.4.1/src/cpu.c:643: undefined reference to 
`ppc_cpu_family_init'
| src/devices/dev_hammerhead.o: In function `dev_hammerhead_access':
| /build/buildd/gxemul-0.4.1/src/devices/dev_hammerhead.c:81: undefined 
reference to `ppc32_pc_to_pointers'
| /build/buildd/gxemul-0.4.1/src/devices/dev_hammerhead.c:83: undefined 
reference to `ppc_pc_to_pointers'
| collect2: ld returned 1 exit status
| make[1]: *** [build] Error 1
| make[1]: Leaving directory `/build/buildd/gxemul-0.4.1'
| make: *** [build-stamp] Error 2
| ******************************************************************************
| Build finished at 20060726-1350
| FAILED [dpkg-buildpackage died]


A full buildd log is available at 
<http://buildd.debian.org/build.php?pkg=gxemul&ver=0.4.1-1&arch=m68k>

Other buildd logs may be available at 
<http://buildd.debian.org/build.php?arch=&pkg=gxemul>

--
Stephen R. Marenka     If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to