Your message dated Wed, 13 Oct 2010 14:34:29 +0200
with message-id <87lj62z2y2....@hepworth.siccegge.de>
and subject line Experimental package is fine
has caused the Debian Bug report #599948,
regarding ecl: FTBFS on mips*: issues in atomic_ops.c
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.)
--
599948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ecl
Version: 10.3.1-2
Severity: serious
Justification: FTBFS
Hi,
your package FTBFS on mips*:
| mipsel-linux-gnu-gcc -fPIC -DPACKAGE_NAME=\"gc\" -DPACKAGE_TARNAME=\"gc\"
-DPACKAGE_VERSION=\"7.1\" "-DPACKAGE_STRING=\"gc 7.1\""
-DPACKAGE_BUGREPORT=\"hans.bo...@hp.com\" -DGC_VERSION_MAJOR=7
-DGC_VERSION_MINOR=1 -DPACKAGE=\"gc\" -DVERSION=\"7.1\" -DGC_LINUX_THREADS=1
-D_REENTRANT=1 -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_DLFCN_H=1
-DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1
-DJAVA_FINALIZATION=1 -DATOMIC_UNCOLLECTABLE=1 -DLARGE_CONFIG=1
-I/build/buildd-ecl_10.3.1-2-mipsel-qJwZTm/ecl-10.3.1/src/gc/include
-fexceptions -I libatomic_ops/src -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2
-fPIC -D_THREAD_SAFE -MT atomic_ops.lo -MD -MP -MF .deps/atomic_ops.Tpo -c
atomic_ops.c -o atomic_ops.o
| atomic_ops.c:74: error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'AO_locks'
| atomic_ops.c:116: error: expected ';', ',' or ')' before '*' token
| atomic_ops.c:124: error: expected ';', ',' or ')' before '*' token
| atomic_ops.c:130: error: expected ';', ',' or ')' before '*' token
| atomic_ops.c:139: error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'init_lock'
| atomic_ops.c: In function 'AO_compare_and_swap_emulation':
| atomic_ops.c:144: error: 'AO_TS_t' undeclared (first use in this function)
| atomic_ops.c:144: error: (Each undeclared identifier is reported only once
| atomic_ops.c:144: error: for each function it appears in.)
| atomic_ops.c:144: error: 'my_lock' undeclared (first use in this function)
| atomic_ops.c:144: error: 'AO_locks' undeclared (first use in this function)
| atomic_ops.c:150: error: 'init_lock' undeclared (first use in this function)
| atomic_ops.c: In function 'AO_compare_double_and_swap_double_emulation':
| atomic_ops.c:180: error: 'AO_TS_t' undeclared (first use in this function)
| atomic_ops.c:180: error: 'my_lock' undeclared (first use in this function)
| atomic_ops.c:180: error: 'AO_locks' undeclared (first use in this function)
| atomic_ops.c:186: error: 'init_lock' undeclared (first use in this function)
| atomic_ops.c: In function 'AO_store_full_emulation':
| atomic_ops.c:215: error: 'AO_TS_t' undeclared (first use in this function)
| atomic_ops.c:215: error: 'my_lock' undeclared (first use in this function)
| atomic_ops.c:215: error: 'AO_locks' undeclared (first use in this function)
| make[4]: *** [atomic_ops.lo] Error 1
Full build logs:
https://buildd.debian.org/status/package.php?p=ecl
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Version: 10.3.1-3
The experimental packages are building against the system atomic-ops
library again and seem to be unaffected by these issues. I'll take a
look at the itanum one.
Regards
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
pgpOIHEndYFwe.pgp
Description: PGP signature
--- End Message ---
