Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libressl: bump to version 2.9.1
Date: Thu, 25 Apr 2019 23:05:41 +0200	[thread overview]
Message-ID: <20190425230541.5ded26e9@windsurf> (raw)
In-Reply-To: <20190425164619.29273-1-aduskett@gmail.com>

Hello,

On Thu, 25 Apr 2019 12:46:19 -0400
aduskett at gmail.com wrote:

> From: Adam Duskett <Aduskett@gmail.com>
> 
> LibreSSL 2.9.1 now has a test that requires libtls.a, however, when building a
> shared library only build, the --disable-static flag is passed to libressl,
> which prevents the building of libtls.a.
> 
> With libtls.a not being built, the following error occurs:
> libressl-2.9.1/tls/.libs/libtls.a', needed by 'handshake_table'.  Stop.
> 
> There are three options to fix this:
> 1) Stick with autotools, and provide a patch that removes building anything in
>    the tests folder.

Or use libtls.la instead of libtls.a. Unfortunately that doesn't work
because their test cases use some internal symbols of their libraries,
which are not exported in the shared libraries. By linking directly to
the static variant, there is no symbol visibility mechanism, and
therefore they can access all symbols.

So, indeed, it's not that easy, and using the CMake build system makes
sense.

So: applied to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-04-25 21:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 16:46 [Buildroot] [PATCH 1/1] package/libressl: bump to version 2.9.1 aduskett at gmail.com
2019-04-25 21:05 ` Thomas Petazzoni [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=20190425230541.5ded26e9@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox