From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/libressl: bump to version 3.0.2
Date: Mon, 18 Nov 2019 09:06:55 +0100 [thread overview]
Message-ID: <20191118090655.16ea0e92@windsurf.home> (raw)
In-Reply-To: <87zhgtsjiq.fsf@dell.be.48ers.dk>
On Mon, 18 Nov 2019 08:58:37 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>
> > commit: https://git.buildroot.net/buildroot/commit/?id=26f42106e8acfd336d8e902da96cd2ac9e63c09d
> > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> > Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
>
> > [Thomas: cherry-picked to master as it fixes a build issue with the
> > musl C library:
> > output/build/libressl-2.9.2/crypto/compat/getprogname_linux.c: In function __getprogname__:
> > output/build/libressl-2.9.2/crypto/compat/getprogname_linux.c:32:2: error: #error "Cannot emulate getprogname"
> > #error "Cannot emulate getprogname"]
>
> Hmm, where do you see that? We also still have 2.9.2 on 2019.08.x and I
> don't see any build issues on the autobuilders:
>
> http://autobuild.buildroot.net/?reason=libressl-%
The autobuilders are not testing libressl. Selecting libressl is part
of a choice, and therefore not randomized by our autobuilders.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-18 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 21:10 [Buildroot] [git commit] package/libressl: bump to version 3.0.2 Thomas Petazzoni
2019-11-18 7:58 ` Peter Korsgaard
2019-11-18 8:06 ` Thomas Petazzoni [this message]
2019-11-18 9:05 ` Peter Korsgaard
2019-11-18 9:42 ` Peter Korsgaard
2019-11-18 12:58 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2019-12-02 8:47 Peter Korsgaard
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=20191118090655.16ea0e92@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.