Hi,
One of the patches we do carry that I'd like to see upstreamed is the
support for multiple files in CONFIG_SITE. Now I'm not just sending the
patch we have as it's pretty horrible:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/autoconf/autoconf/config_site.patch
The use-case is that we have a collection of config.site files: one for
"all builds", one for "all Linux targets", one for "x86-64 targets", and
so on:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/site
(those have grown organically over many years so need a massive review,
but that's the model)
However CONFIG_SITE only takes a single filename, so we patch autoconf
to treat CONFIG_SITE as a list of absolute filenames instead.
I'd like to see this functionality upstreamed but I'd like to discuss
how CONFIG_SITE is parsed first. Should it just be treated as a
space-separated list? Any better suggestions?
Also note that there's potentially very bad interaction: if someone has
done as the manual suggests and dropped a /usr/share/config.site in then
that will be read when doing --prefix=/usr, *even in cross-compile
situations* where /usr is a target prefix and not valid on the host.
Then again this isn't exactly the first time autoconf has this problem.
Thanks,
Ross
