This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Jan 5, 2004, neroden@twcny.rr.com (Nathanael Nerode) wrote:OK, I'll try. First of all, autoconf 2.5x vs. autoconf 2.13; second, multilib subdirs; third, raw_cxx versus regular CXX; fourth, funny options for GCC bootstrap. These are the known problems. There may be other problems relating to autoconf 2.5x 'precious' variables, but they're lost in the noise of the above problems. :-P
I'm disabling the shared cache file for the obvious reason; different subdirectories want to cache different, inconsistent values for the same variables.
You'd better document extensively such inconsistencies such that, when they're addressed, we can re-enable the cache, without the risk of urban legends about problems long solved holding it back.
That's nice. Unfortunately, it doesn't work at the moment. I concluded that it was totally unimportant, compared with (a) getting things working, and (b) allowing modernization of the configure.in scripts.Anyway, naming a config.cache file for the host is wrong. The user is entitled to name a config.cache they want configure to use, and it should be honored at the very least for host packages.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |