[klibc] [klibc:master] Kbuild: Properly disable executable stacks in static builds
Christophe Leroy
christophe.leroy at csgroup.eu
Thu Sep 15 03:06:06 PDT 2022
Hi Ben,
Le 04/08/2022 à 00:51, klibc-bot for Ben Hutchings a écrit :
> Commit-ID: 2acbe15d7a8093cfa295aadc56707892e87a7eaf
> Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=2acbe15d7a8093cfa295aadc56707892e87a7eaf
> Author: Ben Hutchings <ben at decadent.org.uk>
> AuthorDate: Tue, 2 Aug 2022 22:47:14 +0200
> Committer: Ben Hutchings <ben at decadent.org.uk>
> CommitDate: Thu, 4 Aug 2022 00:45:26 +0200
>
> [klibc] Kbuild: Properly disable executable stacks in static builds
>
> I typo'd the variable name KLIBCSTACKFLAGS in the value of
> KLIBCCFLAGS, leaving the stack executable in statically linked
> executables. Fix that.
>
> Executables using a shared library did not have this problem, unless
> they included assembly language sources. C compilers generate the
> no-executable-stack header by default, and the interpreter definition
> that's statically linked into such executables was built with a
> correctly spelt KLIBCSTACKFLAGS as an extra option.
>
> Fixes: c562319cdba0 ("[klibc] Kbuild: Add a per-architecture option to ...")
> Signed-off-by: Ben Hutchings <ben at decadent.org.uk>
>
Do you have any planned date for the delivery of klibc 2.0.11 with the
above fix ?
Thanks
Christophe
More information about the klibc
mailing list