A huge number of config.{guess,sub} instances in the xorg repository are outdated, and fail to detect GNU/kFreeBSD systems properly (and probably other systems as well). Please could you update them? For what GNU/kFreeBSD detection is concerned, any version newer than 2003-10-07 will do. Thanks
Actually, there should not be a single copy of those files anywhere in the X.org source repositories, only in the built tarballs, as they should be added by autoconf et al when generating tarballs, so it sounds like this is really a request to generate tarballs on machines with newer config.* files or newer autoconf versions.
Ah, yes. I didn't notice that. Could you please pass this message on to the person responsible for building release tarballs? Thanks!
argh, closing again. sorry ;)
ARGH. Not this one..
(In reply to comment #2) > Ah, yes. I didn't notice that. > > Could you please pass this message on to the person responsible for building > release tarballs? What autoconf version would you like?
Note that autoconf != config.{guess,sub} The config.guess and config.sub scripts (available in https://savannah.gnu.org/projects/config) are copied by autoconf when AC_CANONICAL_HOST is used. I don't know if there's a standard install path, but in Debian they live in /usr/share/misc. As for the version, anything newer than 2003-10-07 is good enough for GNU/kFreeBSD. You probably want the latest snapshot, though, since that increases chances for your software to build on more systems (these scripts exit with non-zero status when they can't identify the system). Thanks
I upgraded libtool on my build system to 1.5.22 and it seems to be dumping in config.* files with 2005-12-* timestamps in the libtoolized packages it builds now, but that only covers about half our packages.
Ok, thanks. So what about the other half? :)
does debian not have relibtoolize?
marking as fixed, as all new tarballs being made have GNU/kFreeBSD support.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.