GNU bug report logs - #79648
configure.ac sets user-defined CFLAGS

Previous Next

Package: guile;

Reported by: Nikolaos Chatzikonstantinou <nchatz314 <at> gmail.com>

Date: Sat, 18 Oct 2025 09:09:01 UTC

Severity: normal

To reply to this bug, email your comments to 79648 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guile <at> gnu.org:
bug#79648; Package guile. (Sat, 18 Oct 2025 09:09:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Nikolaos Chatzikonstantinou <nchatz314 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sat, 18 Oct 2025 09:09:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Nikolaos Chatzikonstantinou <nchatz314 <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: configure.ac sets user-defined CFLAGS
Date: Sat, 18 Oct 2025 05:07:44 -0400
Hello list,

The CFLAGS variable should not be set in configure.ac. Of course, it
is fine to temporarily set it to a different value to test
compilation, but it should not set "defaults" in CFLAGS, since that
overrides whatever the user sets in the environment.

For example, I compiled with CFLAGS='-O0 g3' to debug a (different)
bug in Guile with gdb, and I did not have any access to macros. After
a lot of head scratching I resorted to asking for help and
https://sourceware.org/bugzilla/show_bug.cgi?id=32381 was pointed out
to me. In short, Guile injected -flto which enables LTO and gdb cannot
trace line numbers correctly.

Instead, configure.ac should be setting defaults in AM_CFLAGS. I will
send a patch moving -flto and -Werror=array-bounds from CFLAGS to
AM_CFLAGS.

Regards,
Nikolaos Chatzikonstantinou




This bug report was last modified 18 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.