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

Bug#674359: marked as done (libextractor-java: FTBFS: conftest.c:35: undefined reference to `EXTRACTOR_loadDefaultLibraries')



Your message dated Sun, 27 May 2012 22:50:59 +0000
with message-id <E1SYmId-0005JQ-Dm@franck.debian.org>
and subject line Bug#674359: fixed in libextractor-java 0.6.0-6
has caused the Debian Bug report #674359,
regarding libextractor-java: FTBFS: conftest.c:35: undefined reference to `EXTRACTOR_loadDefaultLibraries'
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 owner@bugs.debian.org
immediately.)


-- 
674359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674359
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libextractor-java
Version: 0.5.18-8
Severity: serious
Tags: wheezy sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20120524 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [enabled by default]
> configure:7416: $? = 0
> configure:7429: result: no
> configure:7444: checking for gcc option to produce PIC
> configure:7654: result: -fPIC
> configure:7662: checking if gcc PIC flag -fPIC works
> configure:7680: gcc -c -g -O2  -fPIC -DPIC conftest.c >&5
> configure:7684: $? = 0
> configure:7697: result: yes
> configure:7725: checking if gcc static flag -static works
> configure:7753: result: yes
> configure:7763: checking if gcc supports -c -o file.o
> configure:7784: gcc -c -g -O2  -o out/conftest2.o conftest.c >&5
> configure:7788: $? = 0
> configure:7810: result: yes
> configure:7836: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries
> configure:8791: result: yes
> configure:8812: checking whether -lc should be explicitly linked in
> configure:8817: gcc -c -g -O2  conftest.c >&5
> configure:8820: $? = 0
> configure:8835: gcc -shared conftest.o  -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| grep  -lc  \>/dev/null 2\>\&1
> configure:8838: $? = 0
> configure:8850: result: no
> configure:8858: checking dynamic linker characteristics
> configure:9434: result: GNU/Linux ld.so
> configure:9443: checking how to hardcode library paths into programs
> configure:9468: result: immediate
> configure:9482: checking whether stripping libraries is possible
> configure:9487: result: yes
> configure:10288: checking if libtool supports shared libraries
> configure:10290: result: yes
> configure:10293: checking whether to build shared libraries
> configure:10314: result: yes
> configure:10317: checking whether to build static libraries
> configure:10321: result: no
> configure:10413: creating libtool
> configure:11001: checking for ld used by g++
> configure:11068: result: /usr/bin/ld -m elf_x86_64
> configure:11077: checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld
> configure:11092: result: yes
> configure:11143: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries
> configure:12077: result: yes
> configure:12095: g++ -c -g -O2  conftest.cpp >&5
> configure:12098: $? = 0
> configure:12217: checking for g++ option to produce PIC
> configure:12491: result: -fPIC
> configure:12499: checking if g++ PIC flag -fPIC works
> configure:12517: g++ -c -g -O2  -fPIC -DPIC conftest.cpp >&5
> configure:12521: $? = 0
> configure:12534: result: yes
> configure:12562: checking if g++ static flag -static works
> configure:12590: result: yes
> configure:12600: checking if g++ supports -c -o file.o
> configure:12621: g++ -c -g -O2  -o out/conftest2.o conftest.cpp >&5
> configure:12625: $? = 0
> configure:12647: result: yes
> configure:12673: checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries
> configure:12701: result: yes
> configure:12768: checking dynamic linker characteristics
> configure:13344: result: GNU/Linux ld.so
> configure:13353: checking how to hardcode library paths into programs
> configure:13378: result: immediate
> configure:19510: checking for a BSD-compatible install
> configure:19566: result: /usr/bin/install -c
> configure:19577: checking whether ln -s works
> configure:19581: result: yes
> configure:19588: checking whether make sets $(MAKE)
> configure:19609: result: yes
> configure:19704: checking whether gcc accepts -no-cpp-precomp
> configure:19718: result: no
> configure:19724: checking for ANSI C header files
> configure:19888: result: yes
> configure:19900: checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld
> configure:19913: result: yes
> configure:19923: checking for libextractor
> configure:20361: result: --with-extractor not specified
> configure:20378: checking extractor.h usability
> configure:20395: gcc -c -fno-strict-aliasing -g -O2  conftest.c >&5
> configure:20401: $? = 0
> configure:20415: result: yes
> configure:20419: checking extractor.h presence
> configure:20434: gcc -E  conftest.c
> configure:20440: $? = 0
> configure:20454: result: yes
> configure:20487: checking for extractor.h
> configure:20495: result: yes
> configure:20503: checking for EXTRACTOR_loadDefaultLibraries in -lextractor
> configure:20538: gcc -o conftest -fno-strict-aliasing -g -O2   conftest.c -lextractor   >&5
> /tmp/ccnhO3jk.o: In function `main':
> /«PKGBUILDDIR»/conftest.c:35: undefined reference to `EXTRACTOR_loadDefaultLibraries'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/05/24/libextractor-java_0.5.18-8_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



--- End Message ---
--- Begin Message ---
Source: libextractor-java
Source-Version: 0.6.0-6

We believe that the bug you reported is fixed in the latest version of
libextractor-java, which is due to be installed in the Debian FTP archive:

libextractor-java-dbg_0.6.0-6_amd64.deb
  to main/libe/libextractor-java/libextractor-java-dbg_0.6.0-6_amd64.deb
libextractor-java-dev_0.6.0-6_amd64.deb
  to main/libe/libextractor-java/libextractor-java-dev_0.6.0-6_amd64.deb
libextractor-java0_0.6.0-6_amd64.deb
  to main/libe/libextractor-java/libextractor-java0_0.6.0-6_amd64.deb
libextractor-java_0.6.0-6.debian.tar.gz
  to main/libe/libextractor-java/libextractor-java_0.6.0-6.debian.tar.gz
libextractor-java_0.6.0-6.dsc
  to main/libe/libextractor-java/libextractor-java_0.6.0-6.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 674359@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen <holger@debian.org> (supplier of updated libextractor-java package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 28 May 2012 00:36:47 +0200
Source: libextractor-java
Binary: libextractor-java0 libextractor-java-dbg libextractor-java-dev
Architecture: source amd64
Version: 0.6.0-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Holger Levsen <holger@debian.org>
Description: 
 libextractor-java-dbg - Java bindings for GNU libextractor (debug)
 libextractor-java-dev - Java bindings for GNU libextractor (development)
 libextractor-java0 - Java bindings for GNU libextractor
Closes: 674359
Changes: 
 libextractor-java (0.6.0-6) unstable; urgency=low
 .
   * QA upload. (Closes: #674359)
   * debian-rules: clear the dependency_libs field of
     /usr/lib/libextractor_java.la as described in
     http://lists.debian.org/debian-devel/2011/05/msg01003.html
Checksums-Sha1: 
 19b5726c8a279ac9c6d17b1153f776142041839d 2080 libextractor-java_0.6.0-6.dsc
 bee610e75af9a92930ebce67d06612c4e506db54 3529 libextractor-java_0.6.0-6.debian.tar.gz
 c6bf7164b662b4bfd0f5e30e709b8e71e96451ef 10934 libextractor-java0_0.6.0-6_amd64.deb
 acca16d8d66a6de96a5a3b048a35f2be155f34cc 18318 libextractor-java-dbg_0.6.0-6_amd64.deb
 9fc47042873391c8e42f4f98d5cf98faeb11adf2 4840 libextractor-java-dev_0.6.0-6_amd64.deb
Checksums-Sha256: 
 2bc92496db0b9453a4b420e09077cfaafabde1edb0c393d513584694f6a55498 2080 libextractor-java_0.6.0-6.dsc
 570f26444f40721aef3d2dbf0c2a9d73ab56095eebb80b86c1439ec8f5521347 3529 libextractor-java_0.6.0-6.debian.tar.gz
 5b6f4f6f3271e69e5b4f247a1b9bece1804800c4e3b4564a7e98c35ad15ba613 10934 libextractor-java0_0.6.0-6_amd64.deb
 b3e2c55eb2ff89297e3e1d04518826b6d475737efddd46c3dc6344b8bbeea573 18318 libextractor-java-dbg_0.6.0-6_amd64.deb
 3d86c7a8c7c4298d10d04326b20eeb2f14d5238957b561b500bca697f51c5b78 4840 libextractor-java-dev_0.6.0-6_amd64.deb
Files: 
 4ea3aaa18d7db6d0895341057787a203 2080 libs optional libextractor-java_0.6.0-6.dsc
 9f735bfaa209eeb88230a8d2d9c8e34f 3529 libs optional libextractor-java_0.6.0-6.debian.tar.gz
 0fa700e7cbd23db53a7cf763cbfd920d 10934 libs optional libextractor-java0_0.6.0-6_amd64.deb
 3352d1b7d636115ba29d36a1144f5b2e 18318 debug extra libextractor-java-dbg_0.6.0-6_amd64.deb
 ba5a2bcbaa2e64fe3c75ebe2c3b2b2ca 4840 libdevel optional libextractor-java-dev_0.6.0-6_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIVAwUBT8KtgAkauFYGmqocAQgJzg//TfxmqdGDXnsD6p7BtWDgsS6BVsrgQ7QX
3OXj6GhHde5E/OhRyAEN4ENB3I7u3PE854MWwT58wxxyt1SnyNU7cCJ8+fSXYa6t
ZWUGW5AiFgVMgQOGmu/E2AYa2Ow9xFYBmvPMFSMrw5C8ehL+e7Og5mfQgr7+6/Av
KdwAuB6A2XFncDkR+VsyG5cY36akWCrLXwmtfoNCFJD40xDXo/WWl9xvvrKfHRHK
GavHsvyw+8m6WEWTcIHtKwPaYIfl+ZeiEgQ5+xR99XCVe/cTMCT6Y8fXr5w+cYX+
4Rf9M4I5dwp8A7HMpkWaMNsKAwLGSYMWKOmyR6x3BoN+yYj14vtpUWFf+/iYzcIC
QoQc4I9hU2ZNo3Racb7DFCp6i2oYEI/MZg0liGwsYiCAizhsNyq2Ld6TqZcWhdwQ
F59dCC1FGWUL/rvi4i0gCDWXgeDNQbwFuosB3PrGMgL9pT9MjH/PaZ/CN7g2fG79
8ghjflHGdawk4sTKTlDYEg8q4MA1FrEsB000InTPsQ57pNl3LR0K2wM8QmP5V6Cn
5JHf7WVCylMHL2qNA8pdHB3UhAfkuZuBgtjuaSqSho/t1xHqM3JuV56xfjiyOnj5
W3LqGDHUOdZSEke3OSq4d3977X8Q0T5LeO7YJ4HSnsEyMeVS+8LbLDaULcK14ILZ
i6S0WPPqRT4=
=RJ2I
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: