Hi Graham
I think this is worth fixing however I'm not sure the proposed patch is
the right approach - the CMake module it touches actively manages
PY_CFLAGS:
# Note: no quotes, otherwise distutils will execute "/usr/bin/ccache gcc"
# CMake's implicit conversion between strings and lists is wonderful, isn't
it?
set(PY_CFLAGS ${COMPILE_OPTIONS})
cmake_parse_arguments(DU "DISABLE_VTA" "" "" ${ARGN})
if(DU_DISABLE_VTA AND HAS_VTA)
list(APPEND PY_CFLAGS -fno-var-tracking-assignments)
endif()
so although this does result in passing the flags through for the Python
module, it inhibits the function of the CMake module (and I'd like to
get whatever fix we use upstream).
It feels like PY_CFLAGS should be populated with the environmental
CFLAGS but that's not getting passed through correctly? How does
COMPILE_OPTIONS get generated by cmake?
** Changed in: ceph (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: ceph (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: ceph (Ubuntu Oracular)
Status: New => Triaged
** Changed in: ceph (Ubuntu Noble)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078244
Title:
ceph: Does not respect compiler flags for Python extensions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/2078244/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
