<html><body><pre>On <i>Sun Mar 24 17:06:55 PDT 2024</i>
<b>Michele Bucca</b> <a href="mailto:clfs-support%40lists.clfs.org?Subject=Re%3A%20%5BClfs-support%5D%20%5Bclfs-embedded%5D%20Could%20not%20compile%20dropbear%0A%202022.83%20on%20i486-linux-musl&In-Reply-To=%3CCAPa8UMeoeztwfaTOmWKHkLjZv_MnquuoxWy1b01dpQpJ3vAWcA%40mail.gmail.com%3E" title="[Clfs-support] [clfs-embedded] Could not compile dropbear 2022.83 on i486-linux-musl"><michele.bucca at gmail.com</a>> wrote:
> Ok, it seems that if the i486-linux-musl toolchain is built you can't
> use -fstack-protector-all
<a href="https://github.com/GregorR/musl-cross/issues/45" rel="noopener noreferrer">> https://github.com/GregorR/musl-cross/issues/45</a>
>
> So we have two solutions to build dropbear:
> 1. We patch GCC by applying this:
> <a href="https://git.alpinelinux.org/aports/tree/main/gcc/0017-Alpine-musl-package-provides-libssp_nonshared.a.-We-.patch" rel="noopener noreferrer">https://git.alpinelinux.org/aports/tree/main/gcc/0017-Alpine-musl-package-provides-libssp_nonshared.a.-We-.patch</a>
>
> 2. We disable stack protections by prepending CFLAGS="$CFLAGS
> -fno-stack-protector" to configure
>
> Which one is better?<br></pre><div>IMO, the first. Unless it adds a ton of overhead, might as well.<br></div><div><br></div><div>- Alex<br></div><div>(I'm new here, as well)<br></div></body></html>