On 5/11/22 13:31, Rainer Orth wrote: > Hi Martin, > >>>> Subject: [PATCH] configure: add --disable-fix-includes >>> >>> As I've mentioned before, I believe, the command is called fixincludes >>> in current gcc docs, and the option should reflect that, not introduce a >>> name used nowhere else. >> >> No, I can't use it, because even with current master using >> --disable-fixincludes >> means the tool is not built at all. It results with: >> >> g++ -g -DIN_GCC -fPIC -fno-exceptions -fno-rtti >> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings >> -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic >> -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common >> -DHAVE_CONFIG_H -DGENERATOR_FILE -static-libstdc++ -static-libgcc -o >> build/genchecksum \ >> build/genchecksum.o >> ../build-x86_64-pc-linux-gnu/libiberty/pic/libiberty.a >> make: *** No rule to make target >> '../build-x86_64-pc-linux-gnu/fixincludes/fixinc.sh', needed by >> 'stmp-fixinc'. Stop. >> make: *** Waiting for unfinished jobs.... > > and why not just fix that, rather than introducing yet another option?
I would like to, but I don't understant autoconf much :/ @Joseph: Can you please help me why --disable-$foo disables building $foo folder during the build? Thanks, Martin > This error suggests current --disable-fixincludes is useless on it's > own. > > Rainer >
