Bug#981983: libnewlib-arm-none-eabi: CFLAGS vs CFLAGS_FOR_TARGET

To: 981983@bugs.debian.org
Subject: Bug#981983: libnewlib-arm-none-eabi: CFLAGS vs CFLAGS_FOR_TARGET
From: "Deomid \"rojer\" Ryabkov" <rojer@rojer.me>
Date: Tue, 5 Nov 2024 11:51:41 +0200
Message-id: <[🔎] CABFmFwrvj4FsCs-r=1O-E0=haoMV+qunmXN_1FvFgMuk_+mcRA@mail.gmail.com>
Reply-to: "Deomid \"rojer\" Ryabkov" <rojer@rojer.me>, 981983@bugs.debian.org
References: <ef03817a-18bd-9f67-f975-2d2e09a23e4b@gmail.com>

Still a problem with 4.4, reported in Ubuntu: https://bugs.launchpad.net/debian/+source/newlib/+bug/2086618

I found that CFLAGS still have to be provided, even if empty, so my solution is:

CFLAGS := CFLAGS= CFLAGS_FOR_TARGET="-g -O2 -ffunction-sections -fdata-sections"
CFLAGS_NANO := CFLAGS= CFLAGS_FOR_TARGET="-g -Os -ffunction-sections -fdata-sections -fshort-wchar"

Deomid "rojer" Ryabkov

rojer@rojer.me

Reply to:

Prev by Date: libabigail is marked for autoremoval from testing
Next by Date: Re: Bug#1086791: lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant
Previous by thread: libabigail is marked for autoremoval from testing
Next by thread: Re: Bug#1086791: lziprecover: FTBFS on riscv64 due to out-of-bounds access on a constant
Index(es):
- Date
- Thread