mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: chalianis1@gmail.com, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH 1/4] scripts: Makefile.pic: define __NO_FORTIFY without value
Date: Wed, 30 Jul 2025 07:57:40 +0200	[thread overview]
Message-ID: <20250730055743.922932-1-a.fatoum@barebox.org> (raw)

The default for -D without = is to define the symbol to expand to 1.
This is nt what we want, because pbl/string.c defines it without value
leading to a build error. Fix this by defining it empty explicitly
instead.

Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
 scripts/Makefile.pic | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/Makefile.pic b/scripts/Makefile.pic
index a08ee67f4a3e..0cefe350b39e 100644
--- a/scripts/Makefile.pic
+++ b/scripts/Makefile.pic
@@ -13,7 +13,7 @@ picflags-$(CONFIG_ARM64)	:= -fpie
 
 picflags-y			+= -include $(srctree)/include/linux/hidden.h \
 				   -D__fully_pic__ \
-				   -D__NO_FORTIFY \
+				   -D__NO_FORTIFY="" \
 				   -ffreestanding \
 				   -fno-stack-protector \
 				   $(call cc-option,-fno-addrsig) \
-- 
2.39.5




             reply	other threads:[~2025-07-30  5:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  5:57 Ahmad Fatoum [this message]
2025-07-30  5:57 ` [PATCH 2/4] ARM64: configs: multi_v8: disable layerscape temporarily Ahmad Fatoum
2025-08-05  5:43   ` Sascha Hauer
2025-08-11 13:34     ` Ahmad Fatoum
2025-07-30  5:57 ` [PATCH 3/4] ARM: configs: multi: configure CONFIG_CONSOLE_ACTIVATE_ALL_FALLBACK Ahmad Fatoum
2025-07-30  5:57 ` [PATCH 4/4] ARM64: configs: add multi_v8_efi_defconfig Ahmad Fatoum
2025-08-11 13:34 ` [PATCH 1/4] scripts: Makefile.pic: define __NO_FORTIFY without value Sascha Hauer

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=20250730055743.922932-1-a.fatoum@barebox.org \
    --to=a.fatoum@barebox.org \
    --cc=barebox@lists.infradead.org \
    --cc=chalianis1@gmail.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