From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libevent: disable sample programs to workaround static linking issue
Date: Thu, 09 Feb 2017 15:02:17 +0100 [thread overview]
Message-ID: <87wpczmphy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170209102952.6351-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 9 Feb 2017 11:29:51 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes:
> http://autobuild.buildroot.net/results/1e7/1e7027b1b87d88b4517b1b19d3a2ae54c24f2c10/
> http://autobuild.buildroot.net/results/ff7/ff7e010b41e7448d15d20396e9e9bd7319dd493b/
> http://autobuild.buildroot.net/results/269/269a3a76f61c65423ba703a85e94cc003fb75e4c/
> Libevent/libtool gets confused by the library order when statically linking
> the sample programs and passes -lz before -lcrypto even though libcrypto
> uses zlib.
> /bin/bash ./libtool --tag=CC --mode=link .. -o sample/https-client \
> sample/https-client.o sample/hostcheck.o \
> sample/openssl_hostname_validation.o libevent.la \
> libevent_openssl.la -lssl -lcrypto -lz -lz -lcrypto
> libtool: link: .. -o sample/https-client sample/https-client.o \
> sample/hostcheck.o sample/openssl_hostname_validation.o \
> ./.libs/libevent.a ./.libs/libevent_openssl.a \
> -lssl -lz -lcrypto
> ../libcrypto.a(c_zlib.o): In function `zlib_stateful_expand_block':
> c_zlib.c:(.text+0x30): undefined reference to `inflate'
> This is most likely fixable, but as the sample programs aren't installed /
> used, simply skip building them to save time and work around this issue.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-02-09 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 10:29 [Buildroot] [PATCH 1/2] libevent: disable sample programs to workaround static linking issue Peter Korsgaard
2017-02-09 10:29 ` [Buildroot] [PATCH 2/2] libevent: drop openssl static linking workaround Peter Korsgaard
2017-02-09 14:02 ` Peter Korsgaard
2017-02-09 14:02 ` Peter Korsgaard [this message]
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=87wpczmphy.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