From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a
Date: Wed, 16 Jan 2019 15:27:32 +0100 [thread overview]
Message-ID: <20190116152732.26b9c7f9@gmx.net> (raw)
In-Reply-To: <0f76e938-4bda-3168-2699-52727529c04a@mind.be>
Hello Ryan, Arnout,
On Wed, 16 Jan 2019 12:46:54 +0100, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 16/01/2019 02:40, Ryan Coe wrote:
> > I'm getting a build failure in wget with the patch.? The failure is:
> >
> > checking for library containing psl_builtin... no
> > configure: WARNING: *** libpsl was not found. Fallback to builtin cookie checking.
> > checking for ZLIB... yes
> > checking for OPENSSL... no
> > configure: error: Package requirements (openssl) were not met:
> >
> > Package 'openssl', required by 'virtual:world', not found
> >
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> >
> > Alternatively, you may set the environment variables OPENSSL_CFLAGS
> > and OPENSSL_LIBS to avoid the need to call pkg-config.
> > See the pkg-config man page for more details.
> > make: *** [package/pkg-generic.mk:223:
> > /home/ryan/devel/buildroot/output/build/wget-1.20.1/.stamp_configured] Error 1
> >
> >
> > The following tweak makes things build again for me:
> >
> > diff --git a/package/libopenssl/libopenssl.mk b/package/libopenssl/libopenssl.mk
> > index e461e08126..8046995720 100644
> > --- a/package/libopenssl/libopenssl.mk
> > +++ b/package/libopenssl/libopenssl.mk
> > @@ -74,7 +74,7 @@ define HOST_LIBOPENSSL_CONFIGURE_CMDS
> > ???? ??? ./config \
> > ???? ??? --prefix=$(HOST_DIR) \
> > ???? ??? --openssldir=$(HOST_DIR)/etc/ssl \
> > -??? ??? --libdir=$(HOST_DIR)/lib \
> > +??? ??? --libdir=lib \
> > ???? ??? -Wl,-rpath,'$(HOST_DIR)/lib' \
> > ???? ??? shared \
> > ???? ??? zlib-dynamic \
> > @@ -90,7 +90,7 @@ define LIBOPENSSL_CONFIGURE_CMDS
> > ???? ??? ??? linux-$(LIBOPENSSL_TARGET_ARCH) \
> > ???? ??? ??? --prefix=/usr \
> > ???? ??? ??? --openssldir=/etc/ssl \
> > -??? ??? ??? --libdir=/lib \
> > +??? ??? ??? --libdir=lib \
> > ???? ??? ??? $(if $(BR2_TOOLCHAIN_HAS_THREADS),threads,no-threads) \
> > ???? ??? ??? $(if $(BR2_STATIC_LIBS),no-shared,shared) \
> > ???? ??? ??? no-rc5 \
>
> That is definitely not good, because it breaks things in other places.
>
> I think it's worth a try to remove the --libdir entirely instead, upstream is
> supposed to have fixed the libdir handling to correspond to autotools
> conventions. And if it doesn't work, we should fix it with an upstreamable patch.
Removing both libdir lines works (and fixes the installation path of the openssl.pc file which
fixes the wget compile problem), will add it to the next patch iteration...
Regards,
Peter
>
> Regards,
> Arnout
next prev parent reply other threads:[~2019-01-16 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 22:42 [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Peter Seiderer
2019-01-15 22:42 ` [Buildroot] [PATCH v4 2/2] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Peter Seiderer
2019-01-16 1:40 ` [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Ryan Coe
2019-01-16 11:46 ` Arnout Vandecappelle
2019-01-16 14:27 ` Peter Seiderer [this message]
2019-01-16 5:52 ` Baruch Siach
2019-01-16 13:58 ` Vadim Kochan
2019-01-17 18:43 ` Peter Seiderer
2019-01-22 11:23 ` Arnout Vandecappelle
2019-01-22 21:08 ` Peter Korsgaard
2019-01-23 14:29 ` Arnout Vandecappelle
2019-01-23 16:15 ` Peter Korsgaard
2019-01-23 22:44 ` Arnout Vandecappelle
2019-01-23 23:03 ` Peter Korsgaard
2019-01-25 23:27 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2019-01-16 11:43 Patrick Havelange
2019-01-16 14:24 ` Peter Seiderer
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=20190116152732.26b9c7f9@gmx.net \
--to=ps.report@gmx.net \
--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