Have configure.ac tolerate unregistered builds or new platforms
ggreif at gmail.com
Wed Jan 18 16:23:02 CET 2012
I am all-for a new switch (say "--with-unregisterised").
Gaby, should I build in one on my fork?
On 1/18/12, Ian Lynagh <igloo at earth.li> wrote:
> On Mon, Jan 16, 2012 at 12:42:19PM -0600, Gabriel Dos Reis wrote:
>> -- have both checkArch and checkOS not abort configuration
>> they should normalize arch and os known to be troublesome
>> and report ArchUnknown and OsUknown for arches and OSes
>> not known to GHC.
> The rationale for the current behaviour is that it will catch typos and
> incorrect arch names (e.g. using x86 rather than i386). The assumption
> is that people will make typos more frequently than there will be ports
> to new arches (as there are a limited number of arches to which one
> could port), and that it's more useful to catch the typos (I'm not sure
> OTTOMH what happens if you typo otherwise; you might end up with a
> complete unregisteriesd build. By contrast, when porting to a new
> platform, configure stops immediately and tells you what's wrong).
> Cvs-ghc mailing list
> Cvs-ghc at haskell.org
More information about the Cvs-ghc