From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-19
Date: Thu, 20 Nov 2014 22:41:41 +0100 [thread overview]
Message-ID: <87zjbleei2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <XnsA3EBC78DF44F4berndkuhlsPkbjNfxxIA@bernd-kuhls.de> (Bernd Kuhls's message of "Thu, 20 Nov 2014 19:37:02 +0100")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
Hi,
>> Bernd, can you have a look?
> I still[1] can not reproduce the bug on my machine. Apparently it happens
> only on Peter.s autobuilder: http://autobuild.buildroot.net/?reason=clamav-
> 0.98.4.
I did a manual test build on gcc16 and I see:
(with make CLAMAV_MAKE_OPTS='V=1' BR2_JLEVEL=1 clamav)
libtool: link: /home/peko/tmp/buildroot/output/host/usr/bin/armv5-ctng-linux-gnueabi-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -fno-strict-aliasing -o clamscan output.o getopt.o optparser.o actions.o misc.o clamscan.o manager.o ../libclamav/.libs/libclamav.so -L/home/peko/tmp/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib -L/usr/lib -lbz2 -lssl -lcrypto -lz -lm -ldl -lpthread -Wl,-rpath -Wl,/home/peko/tmp/buildroot/output/build/clamav-0.98.5/libclamav/.libs
../libclamav/.libs/libclamav.so: undefined reference to `bzDecompress'
../libclamav/.libs/libclamav.so: undefined reference to `bzDecompressInit'
../libclamav/.libs/libclamav.so: undefined reference to `bzDecompressEnd'
collect2: error: ld returned 1 exit status
As the -L/usr/lib hints of, the bzip2 detection is failing. From
config.log:
configure:17633: checking how to link with libbz2
configure:18093: result: /usr/lib/libbz2.so
configure:18134: checking for BZ2_bzDecompressInit in -lbz2
configure:18159: /home/peko/tmp/buildroot/output/host/usr/bin/armv5-ctng-linux-gnueabi-gcc -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/home/peko/tmp/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/include -L/usr/lib conftest.c -lbz2 -ldl >&5
/usr/lib/libbz2.so: file not recognized: File format not recognized
> @Peter: Could you please try this patch locally on your autobuilder?
> --- a/package/clamav/clamav.mk
> +++ b/package/clamav/clamav.mk
> @@ -16,6 +16,7 @@ CLAMAV_DEPENDENCIES = openssl zlib $(if $(BR2
> _NEEDS_GETTEXT_IF_LOCALE),gettext)
> # mmap cannot be detected when cross-compiling, needed for mempool support
> CLAMAV_CONF_ENV = \
> + LIBBZ2_PREFIX=$(STAGING_DIR)/usr \
> ac_cv_c_mmap_private=yes
Thanks, but that doesn't work:
Applying buildroot-libtool-v2.4.patch using patch:
patching file ltmain.sh
(cd /home/peko/tmp/buildroot/output/build/clamav-0.98.5/ && ... \
LIBBZ2_PREFIX=/home/peko/tmp/buildroot/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr ac_cv_c_mmap_private=yes CONFIG_SITE=/dev/null ./configure
..
checking how to link with libbz2... /usr/lib/libbz2.so
checking for BZ2_bzDecompressInit in -lbz2... no
checking bzlib.h usability... yes
checking bzlib.h presence... yes
and it naturally still fails at the linking step.
Looking closer at the configure script I see we need to pass
ac_cv_libbz2_libs and ac_cv_libbz2_ltlibs instead. With that done it
works.
I'll cook a patch to do so.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-11-20 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-19 Thomas Petazzoni
2014-11-20 8:42 ` Baruch Siach
2014-11-20 9:38 ` Peter Korsgaard
2014-11-20 8:44 ` Thomas Petazzoni
2014-11-20 9:09 ` Baruch Siach
2014-11-20 9:16 ` Thomas Petazzoni
2014-11-20 9:36 ` Peter Korsgaard
2014-11-20 10:27 ` Thomas Petazzoni
2014-11-20 10:48 ` Peter Korsgaard
2014-11-20 18:37 ` Bernd Kuhls
2014-11-20 21:41 ` Peter Korsgaard [this message]
2014-11-20 19:58 ` Alexey Brodkin
2014-11-21 8:20 ` Thomas Petazzoni
2014-11-20 20:07 ` Bernd Kuhls
2014-11-21 18:43 ` Bernd Kuhls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjbleei2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox