From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] netsnmp: fix static build with openssl
Date: Sun, 9 Sep 2018 15:09:19 +0200 [thread overview]
Message-ID: <20180909150919.546beda4@windsurf.home> (raw)
In-Reply-To: <CAPi7W81tAT9=LeVBT6gCR7a57S72ynpganrm4rSLq5viv4oUqw@mail.gmail.com>
Hello,
On Sun, 9 Sep 2018 14:43:41 +0200, Fabrice Fontaine wrote:
> Because the last time I tried to use pkg-config, the upstream project
> decided to refuse the merge request and use ac_search_libs instead:
> https://gitlab.com/muttmua/mutt/merge_requests/25 :-(
I think in such cases, we should propose a patch that uses pkg-config
if available, and if not falls back to AC_CHECK_LIB or other macros. If
pkg-config is available, then static linking will work, if not, it will
continue to fail like it used to.
> I know that netsnmp is already using pkg-config, but only for libnl perhaps
> they would agree to use it also for ssl. I'll ask them and if they agree
> I'll update my patch.
Sure. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-09 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 8:51 [Buildroot] [PATCH 1/1] netsnmp: fix static build with openssl Fabrice Fontaine
2018-09-09 12:16 ` Thomas Petazzoni
2018-09-09 12:43 ` Fabrice Fontaine
2018-09-09 13:09 ` Thomas Petazzoni [this message]
2018-09-17 20:37 ` Giulio Benetti
2018-09-17 20:39 ` [Buildroot] [PATCH] netsnmp: fix static build failure due to missing -lssl and -lz Giulio Benetti
2018-10-11 20:46 ` Peter Korsgaard
2018-10-11 20:52 ` Giulio Benetti
2018-09-17 20:43 ` [Buildroot] [PATCH 1/1] netsnmp: fix static build with openssl Fabrice Fontaine
2018-09-17 21:22 ` Thomas Petazzoni
2018-09-17 21:44 ` Giulio Benetti
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=20180909150919.546beda4@windsurf.home \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.