Closed zeule closed 2 years ago
I had this issue, and solved it by removing some flags from CXXFLAGS which were being set in my environment. The flags in my case were the following (I haven't narrowed it down to which ones):
CXXFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASSERTIONS -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -Og -fvar-tracking-assignments -fdebug-prefix-map=/home/dcal/.cache/yay/fswatch/src=/usr/src/debug
Apologies for the late answer. I've never experienced this problems in the development environments I've tried. Was this a vanilla environment, or was it customised in any way? @hedgepigdaniel what are you referring to exactly when you say 'some flags which were being set in my environment'? Who/what was setting those flags?
Feel free to open this again if still relevant.
Environment is AMD64 Gentoo Linux with GCC 10.1 (and CLang is also installled). The configure step fails.
I run
configure
as follows:For unknown reason the configure script jumps from GCC to CLang in the middle of the process:
and after that basically every test fails.
If I use the
./autogen.sh
file and then simply./configure
, the configuration step passes but then in theMakefile
GCC is replaced with CLang:config.log