Hi Bruno, Am 01.12.2020 um 23:13 schrieb Bruno Haible <br...@clisp.org>: >> Nope, neither —host nor —cache-file, but what differs is that I pass -m64 in >> CFLAGS >> and not as part of CC. > > I see. > > I have submitted a patch to improve the Autoconf documentation on this topic: > <https://savannah.gnu.org/support/?110387>.
I vaguely remember that I had problems in the past by putting anything else than the compiler executable path in CC when also libtool was involved. There was some detection of the tagsfilepath depending on that IIRC, but that was years ago. I’ll have selection code in our buildsystem now where the archflags should go and gettext 2020-11-16 now built cleanly. For 0.21 I have the failing test test-fopen-gnu, is this safe to ignore so I can release a package for the built 0.21? After that I can proceed with the gnulib CI. Best regards — Dago -- "You don't become great by trying to be great, you become great by wanting to do something, and then doing it so hard that you become great in the process." - xkcd #896
