cvs commit: fptools configure.in acconfig.h fptools/mk config.h.in fptools/libraries/base/Foreign/C Error.hs fptools/libraries/ba se/cbits errno.c fptools/libraries/base/include HsBase.h errUtils.h

[Simon Marlow]

  Modified files:
    .                    configure.in acconfig.h 
    mk                   config.h.in 
    libraries/base/Foreign/C Error.hs 
    libraries/base/cbits errno.c 
    libraries/base/include HsBase.h 
  Removed files:
    libraries/base/include errUtils.h 
  Log:
  Re-instate the checking for the values of errno constants at configure
  time.  The problem with doing it using foreign calls is simply that
  this tickles a bad case in the code gen machinery, which in this case
  results in an extra 10-20k of goop ending up in pretty much every
  binary, and it impacts GC performance too.
  
  This has some portability implications, but the situation is no worse
  than before.  To reliably cross-compile for a new platform you need to
  build a set of .hc files for the libraries using a config.h generated on
  the *target* machine.  (at some point we'll formalise the
  cross-compilation story, but that's another thing on the todo list...)
  
  Revision  Changes    Path
  1.170     +2 -0      fptools/configure.in
  1.35      +309 -3    fptools/acconfig.h
  1.57      +294 -0    fptools/mk/config.h.in
  1.12      +98 -201   fptools/libraries/base/Foreign/C/Error.hs
  1.5       +1 -595    fptools/libraries/base/cbits/errno.c
  1.14      +1 -2      fptools/libraries/base/include/HsBase.h