2 If your package uses config.guess and/or config.sub, then it probably
3 relies on the autotools as its build system. In this case, you should
4 use the autotools-package infrastructure, which will take care of updating
5 the config.guess and/or config.sub files appropriately. See the
6 Buildroot documentation for details about the autotools-package
9 If for some reason your package does not use the autotools-package
10 infrastructure, you can request the config.guess and/or config.sub
11 files of your package to be updated by using:
13 $(call CONFIG_UPDATE,directory-of-your-package-sources)
16 GNU config is now managed in git, so to update:
18 # git clone git://git.savannah.gnu.org/config.git
19 # cp config/config.* .
20 # for p in $(ls patches/*.patch); do patch -p1 < $p; done
23 Currently no patches are needed, but they may be needed again in the
26 The current Buildroot version is based on the Git commit
27 dafd8e767ec87b90aac62f0fcedd11944c84b50a of the config.git repository.