Hi Helmut! On Tue, May 12, 2026 at 11:45 PM Helmut Grohne <[email protected]> wrote: > > I noticed that blt fails to build from source when the CC variable is > exported. It does not matter what you export it to. It can be "cc", > "gcc" or "x86_64-linux-gnu-gcc" or even "false" or "true". The behavior > is always the same: It discovers a compiler and then fails to find any > header. With the help of Timo Roehling and Tobias Frost, I discovered > that the root cause for the problem resides in configure.in. The > AC_PROG_CC macro is conditionalized. When passing --with-cc, exporting > CC or setting the blt_cv_prog_cc cache variable, AC_PROG_CC is skipped > over. Doing so breaks all sorts of other checks. Instead, we should set > CC to whatever we prefer and then always run AC_PROG_CC. Then blt no > longer FTBFS. Please consider applying the attached patch and forwarding > it upstream.
Thank you for the analysis and for the patch! I'll apply it at the next upload. As for sending it upstream, BLT did not have any release for a very long time, its current development is a bit stalled, but as far as I can see, configure.ac in Git does not require this patch. It runs AC_PROG_CC unconditionally. Cheers! -- Sergei Golovan
