On Jul 26, 2023, at 14:38, Jason Yip via Discussions on LilyPond development <lilypond-devel@gnu.org> wrote: > > * ../configure > --prefix=/home/lj/projects/internships/2023/lilypond/build/release > --disable-debugging --disable-optimising --enable-checking > --enable-profiling 'CC=ccache clang' 'CXX=ccache clang++' > 'CXXFLAGS=-std=c++11 -march=native -O0 -g -pedantic -fno-plt > -Wformat -Werror=format-security -Wno-unused-command-line-argument > -fstack-clash-protection -fstack-protector-strong -fcf-protection > -fuse-ld=mold -Wp,-D_GLIBCXX_ASSERTIONS' > LDFLAGS=-Wl,--sort-common,--as-needed,-z,defs,-z,relro,-z,now > PYTHON=/usr/bin/python > * make > > My configure args have always worked in the past, but not this morning
> 'CC=ccache clang' 'CXX=ccache clang++' Have you tried clearing the cache? > CXXFLAGS=-std=c++11 Why this? We started using C++14 in June 2022. We are currently building with -std=c++17, though we haven't intentionally started using C++17 features. > -pedantic I'm surprised that this doesn't complain about ##__VA_ARGS__, but I guess that Clang is not as pedantic as GCC. You're using a some compiler features that I don't immediately recognize. Have you tried just `autogen.sh --ci`? — Dan
