From: Diederik de Haas <didi.debian@cknow.org>
To: "Ian Rogers" <irogers@google.com>,
"Uwe Kleine-König" <ukleinek@debian.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools lib symbol: Use -D_FORTIFY_SOURCE=2 for non-debug builds
Date: Mon, 01 Apr 2024 13:51:23 +0200 [thread overview]
Message-ID: <3441159.KmgsX75shj@bagend> (raw)
In-Reply-To: <14858d07-abc2-48f9-329a-6d5a4faceeb9@debian.org>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
On Sunday, 30 April 2023 11:11:26 CEST Uwe Kleine-König wrote:
> On 4/29/23 23:05, Ian Rogers wrote:
> > On Apr 24, 2023 at 3:28 AM Uwe Kleine-König <ukleinek@debian.org> wrote:
> >> Commit 160be157eaba ("tool lib symbol: Add Makefile/Build") failed to
> >> define _FORTIFY_SOURCE to 2, probabaly this was cut&pasted from other
> >> Makefiles with the same problem.
> >>
> >> Fixes: 160be157eaba ("tool lib symbol: Add Makefile/Build")
> >> Signed-off-by: Uwe Kleine-König <ukleinek@debian.org>
> >
> > Acked-by: Ian Rogers <irogers@google.com>
>
> Thanks
>
> > Same problem here I think:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/to
> > ols/lib/api/Makefile#n42
> Indeed, and similar patch here:
>
> https://lore.kernel.org/all/20230424102049.58338-1-ukleinek@debian.org/
I noticed this (and the other linked) patch haven't been merged yet.
What's needed to move this forward?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-04-01 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:28 Uwe Kleine-König
2023-04-29 21:05 ` Ian Rogers
2023-04-30 9:11 ` Uwe Kleine-König
2024-04-01 11:51 ` Diederik de Haas [this message]
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=3441159.KmgsX75shj@bagend \
--to=didi.debian@cknow.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ukleinek@debian.org \
/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
Powered by JetHome