1*4882a593Smuzhiyun--- HOWTO --- 2*4882a593SmuzhiyunIf your package uses config.guess and/or config.sub, then it probably 3*4882a593Smuzhiyunrelies on the autotools as its build system. In this case, you should 4*4882a593Smuzhiyunuse the autotools-package infrastructure, which will take care of updating 5*4882a593Smuzhiyunthe config.guess and/or config.sub files appropriately. See the 6*4882a593SmuzhiyunBuildroot documentation for details about the autotools-package 7*4882a593Smuzhiyuninfrastructure. 8*4882a593Smuzhiyun 9*4882a593SmuzhiyunIf for some reason your package does not use the autotools-package 10*4882a593Smuzhiyuninfrastructure, you can request the config.guess and/or config.sub 11*4882a593Smuzhiyunfiles of your package to be updated by using: 12*4882a593Smuzhiyun 13*4882a593Smuzhiyun<pkg>_POST_PATCH_HOOKS += UPDATE_CONFIG_HOOK 14*4882a593Smuzhiyun 15*4882a593Smuzhiyun--- UPDATE --- 16*4882a593SmuzhiyunRun the script 'update' in this directory, and commit the result. 17*4882a593Smuzhiyun 18*4882a593SmuzhiyunThe current Buildroot version is based on this commit of the config.git 19*4882a593Smuzhiyunrepository (leave alone on its own line, the script updates it): 20*4882a593Smuzhiyun 21*4882a593Smuzhiyund7a4dee7cc25e332b990d0a6d9f0ddd42cb33cf5 22