From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Wander Lairson Costa <wander@redhat.com>
Cc: williams@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 0/3] Improve Makefile robustness and explicitness
Date: Tue, 11 Nov 2025 15:50:20 +0100 [thread overview]
Message-ID: <20251111145020.C7DI111V@linutronix.de> (raw)
In-Reply-To: <20251107161729.320087-1-wander@redhat.com>
On 2025-11-07 13:17:25 [-0300], Wander Lairson Costa wrote:
> The first two patches add checks to conditionally use compiler flags
> -mno-omit-leaf-frame-pointer and -fcf-protection, preventing build
> failures on systems where they are not supported.
I don't know what this part of but shouldn't the Makefile just consume
what the buildsystem provided and not randomly strip CFLAGS?
Sebastian
next prev parent reply other threads:[~2025-11-11 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:17 [PATCH 0/3] Improve Makefile robustness and explicitness Wander Lairson Costa
2025-11-07 16:17 ` [PATCH 1/3] Makefile: Conditionally add -mno-omit-leaf-frame-pointer Wander Lairson Costa
2025-11-07 16:17 ` [PATCH 2/3] Makefile: Improve compiler flag detection for -fcf-protection Wander Lairson Costa
2025-11-07 16:41 ` Derek Barbosa
2025-11-07 16:17 ` [PATCH 3/3] Makefile: Explicitly run the 'test' target in the tests directory Wander Lairson Costa
2025-11-11 14:50 ` Sebastian Andrzej Siewior [this message]
2025-11-11 15:35 ` [PATCH 0/3] Improve Makefile robustness and explicitness Derek Barbosa
2025-11-11 15:50 ` Sebastian Andrzej Siewior
2025-11-11 16:29 ` Derek Barbosa
2025-11-12 7:41 ` Sebastian Andrzej Siewior
2025-11-12 12:12 ` Wander Lairson Costa
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=20251111145020.C7DI111V@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=wander@redhat.com \
--cc=williams@redhat.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