From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
"J. Neuschäfer via buildroot" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v5] Config.in: ban textrels on musl toolchains
Date: Wed, 31 Jul 2024 00:03:59 +0200 [thread overview]
Message-ID: <20240731000359.270740ba@windsurf> (raw)
In-Reply-To: <20240719-ztext-v5-1-ec46696d4ed9@gmx.net>
Hello J,
On Fri, 19 Jul 2024 17:27:19 +0200
J. Neuschäfer via buildroot <buildroot@buildroot.org> wrote:
> +# See also: https://www.openwall.com/lists/musl/2020/09/25/4
> +ifeq ($(BR2_TOOLCHAIN_USES_MUSL):$(BR2_STATIC_LIBS),y:)
> +TARGET_LDFLAGS += -Wl,-z,text
> +endif
Unfortunately, this change is breaking the build of gnu-efi:
http://autobuild.buildroot.net/results/e3d/e3dec7e0323a3fcb07269b3f9e73becaafeedecd/build-end.log
It seems like gnu-efi uses $(TARGET_LDFLAGS) directly as arguments to
the linker, not as arguments to gcc-used-as-a-linker, and the linker
doesn't know about -Wl,-z,-text.
So, either we to "-z text" which I believe is understood by both gcc
and ld, or we somehow fix gnu-efi.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-30 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 15:27 [Buildroot] [PATCH v5] Config.in: ban textrels on musl toolchains J. Neuschäfer via buildroot
2024-07-22 16:31 ` Thomas Petazzoni via buildroot
2024-07-30 22:03 ` Thomas Petazzoni via buildroot [this message]
2024-08-04 22:31 ` J. Neuschäfer via buildroot
2024-08-13 9:09 ` yann.morin
2024-08-23 10:21 ` J. Neuschäfer via buildroot
2024-08-24 19:36 ` J. Neuschäfer via buildroot
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=20240731000359.270740ba@windsurf \
--to=buildroot@buildroot.org \
--cc=j.neuschaefer@gmx.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.