When you type ./configure, the GNU Build System automatically spends the next ten minutes reminiscing about every major and minor unix variant created since 1971

@jordyd if only my distribution's maintainers had a way to tell the software running the toolchain packaged by my distribution's maintainers about the toolchain packaged by my distribution's maintainers

@bb010g @jordyd with my upstream author hat on: if only there was a way for my package to find the toolchain on any system.

Oh wait, there is.

@GyrosGeier @jordyd this would just be standardizing on a system-toolchain information file format, right? like a JSON file, telling you about quirks if it's present, and if it's not present the autoconf song-and-dance can generate one for you?

pkgconfig does this for libraries, instead of running detection on /usr/lib/.


@bb010g @jordyd the problem with any tool is that it needs to cover the existing use cases as well, or it is a regression. It was a long battle to get pkg-config to work with cross-compilation, and CMake's toolchain files are also a step backwards compared to interrogating the compiler, because now I have to predict what packages may look for, and provide the value by hand.

Maybe the other way round would be better: packages list values they need, and the configure tool checks If they are known

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!