[Buildroot] [git commit] package/libressl: bump to version 3.0.2

[Thomas Petazzoni]

On Mon, 18 Nov 2019 10:05:24 +0100
Peter Korsgaard <peter at korsgaard.com> wrote:

> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at bootlin.com> writes:  
> 
>  > On Mon, 18 Nov 2019 08:58:37 +0100
>  > Peter Korsgaard <peter at korsgaard.com> wrote:  
> 
>  >> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at 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 at gmail.com>
>  >> > Signed-off-by: Peter Korsgaard <peter at 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.  
> 
> Ahh yes, true. So presumably this should also be cherry picked for
> 2019.08.x?

Yes, I would assume it is needed for 2019.08.x as well, but I have not
tested if the build issue was really present.

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