From: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: "Romain Naour" <romain.naour@gmail.com>,
"Giulio Benetti" <giulio.benetti@benettiengineering.com>,
"J . Neuschäfer" <j.neuschaefer@gmx.net>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/3] toolchain/wrapper: move -ztext to the toolchain wrapper
Date: Fri, 23 Aug 2024 13:02:58 +0200 [thread overview]
Message-ID: <ZshsYmf4qZcXkEZX@probook> (raw)
In-Reply-To: <cover.1723543467.git.yann.morin@orange.com>
On Tue, Aug 13, 2024 at 12:04:28PM +0200, yann.morin@orange.com wrote:
> From: "Yann E. MORIN" <yann.morin@orange.com>
>
> Hello All!
>
> Following a discussion with Thomas , we were both left wondering why
> -ztext was not handled in the toolchain wrapper, like the other similar
> flags are.
Simple answer: I didn't know about the toolchain wrapper at the time :-)
> This small series is an attempt at making it so.
Thanks for taking care of this!
-- jn
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-23 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 10:04 [Buildroot] [PATCH 0/3] toolchain/wrapper: move -ztext to the toolchain wrapper yann.morin
2024-08-13 10:04 ` [Buildroot] [PATCH 1/3] toolchain/wrapper: check unsafe paths earlier yann.morin
2025-05-18 9:52 ` Peter Korsgaard
2025-06-04 18:20 ` Arnout Vandecappelle via buildroot
2024-08-13 10:04 ` [Buildroot] [PATCH 2/3] toolchain/wrapper: check we did not add more args than expected yann.morin
2025-05-18 12:51 ` Peter Korsgaard
2024-08-13 10:04 ` [Buildroot] [PATCH 3/3] toolchain/wrapper: move -ztext from LDFLAGS to toolchain wrapper yann.morin
2024-08-14 5:54 ` yann.morin
2024-08-23 11:02 ` J. Neuschäfer via buildroot [this message]
2024-09-13 17:06 ` [Buildroot] [PATCH 0/3] toolchain/wrapper: move -ztext to the " Markus Mayer 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=ZshsYmf4qZcXkEZX@probook \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=j.neuschaefer@gmx.net \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox