Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:24:28 +0100	[thread overview]
Message-ID: <20190116152428.72a0888c@gmx.net> (raw)
In-Reply-To: <CAKKE0ZGrgnuVRzqeMvGvQfdn8mYyrGuPr_A64x6cO9LDnzqjRA@mail.gmail.com>

Hello Patrick,

On Wed, 16 Jan 2019 12:43:30 +0100, Patrick Havelange <patrick.havelange@essensium.com> wrote:

> Hello all,
> First sorry for not replying properly, I was not subscribed to the ML yet.

No problem (and every feedback/test is valuable ;-) )....
  
> About the breakage of wget, it is indeed because openssl got installed
> in /lib instead of /usr/lib/
> 
> So I think only the second part of the patch of Ryan Coe is needed, ie :

I tested the suggestion by Arnout and removing both libdir lines works fines
(and fixes the installation path of the openssl.pc file which fixes the wget
compile problem)...

Regards,
Peter

> 
> diff --git a/package/libopenssl/libopenssl.mk b/package/libopenssl/libopenssl.mk
> index e461e08..c3cb98a 100644
> --- a/package/libopenssl/libopenssl.mk
> +++ b/package/libopenssl/libopenssl.mk
> @@ -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 \
> 
> I got the same issue with the axel package and it was enough to fix it.
> 
> BR,
> 
> Patrick Havelange
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-01-16 14:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 11:43 [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Patrick Havelange
2019-01-16 14:24 ` Peter Seiderer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-15 22:42 Peter Seiderer
2019-01-16  1:40 ` Ryan Coe
2019-01-16 11:46   ` Arnout Vandecappelle
2019-01-16 14:27     ` Peter Seiderer
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

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=20190116152428.72a0888c@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