All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@debian.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org,
	Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH] tools lib symbol: Use -D_FORTIFY_SOURCE=2 for non-debug builds
Date: Sun, 30 Apr 2023 11:11:26 +0200	[thread overview]
Message-ID: <14858d07-abc2-48f9-329a-6d5a4faceeb9@debian.org> (raw)
In-Reply-To: <CAP-5=fUOL0FmtMbLQtRx2-_i6uvbsBLsxaAg54x8umT4npT7iA@mail.gmail.com>

On 4/29/23 23:05, Ian Rogers wrote:
> On Mon, 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/tools/lib/api/Makefile#n42

Indeed, and similar patch here:

	https://lore.kernel.org/all/20230424102049.58338-1-ukleinek@debian.org/

Best regards
Uwe

  reply	other threads:[~2023-04-30  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 10:28 [PATCH] tools lib symbol: Use -D_FORTIFY_SOURCE=2 for non-debug builds Uwe Kleine-König
2023-04-29 21:05 ` Ian Rogers
2023-04-30  9:11   ` Uwe Kleine-König [this message]
2024-04-01 11:51     ` Diederik de Haas

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=14858d07-abc2-48f9-329a-6d5a4faceeb9@debian.org \
    --to=ukleinek@debian.org \
    --cc=acme@redhat.com \
    --cc=didi.debian@cknow.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.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 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.