From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] netsnmp: fix static build failure due to missing -lssl and -lz
Date: Sat, 20 Oct 2018 18:59:53 +0200 [thread overview]
Message-ID: <87ftx0a706.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181011204516.D4311835D7@busybox.osuosl.org> (Peter Korsgaard's message of "Thu, 11 Oct 2018 22:26:42 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=13722d58f77d0e9fea9eefc50bf083d19f835433
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> During configure some checking needing -lssl and -lz don't have them
> appended to linker tail. Since we are building static this leads to
> configure failure because of mandatory functions lack produces:
> "configure: error: The DTLS based transports require the libssl library
> from OpenSSL to be available and support DTLS"
> - Add 1 patch to fix -lssl lack in configure and .ac modules:
> upstreamed: https://sourceforge.net/p/net-snmp/code/ci/bd59be8e4e339870a1400f6866a7b73ca11f6460/
> - Add 2 patches to fix -lz lack in configure and .ac modules:
> 1 upstreamed: https://sourceforge.net/p/net-snmp/code/ci/13da2bcde8e22dd0127a668374fdf79bed04d353/
> 1 in Merge Request: https://sourceforge.net/p/net-snmp/code/merge-requests/19/
> - Add NETSNMP_AUTORECONF = YES
Committed to 2018.02.x and 2018.08.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-10-20 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 20:26 [Buildroot] [git commit] netsnmp: fix static build failure due to missing -lssl and -lz Peter Korsgaard
2018-10-12 20:08 ` Thomas Petazzoni
2018-10-12 21:00 ` Giulio Benetti
2018-10-15 21:59 ` [Buildroot] [PATCH] netsnmp: improve linking avoiding useless -lz listing in shared build Giulio Benetti
2018-10-19 22:14 ` Peter Korsgaard
2018-10-20 17:00 ` Peter Korsgaard
2018-10-20 16:59 ` 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=87ftx0a706.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