I'm getting a build error with the latest darcs-unstable tree on my Mac 
OS X 10.4.11 (Intel) machine:

[ghc] src/Darcs/External.o

/tmp/ghc26955_0/ghc26955_0.hc:6:20:
      error: termio.h: No such file or directory
make: *** [src/Darcs/External.o] Error 1

Earlier, the configure step gives this output:

checking termio.h usability... no
checking termio.h presence... no
checking for termio.h... no

but it looks like the build is still expecting to find termio.h on the 
system.

I'm able to work around the issue by editing GNUmakefile:

ifeq ($(HAVE_TERMIO_H),True)
# This termio bit is a grim hack for Solaris 10 (at least).
# Without it, SGTTY isn't declared.  Something in the ghc C headers
# which get included before term.h in the generated C is clobbering
# it.  (If you edit that C and put the curses.h and term.h first, the
# error goes away.)
GHCFLAGS_src__Darcs__External.o += '-\#include <termio.h>'
endif

After removing this section of the makefile, I'm able to complete the build.

Keith Browne
tuxedo@funkrehab.com

On Mon, Dec 17, 2007 at 03:49:09PM -0000, Keith Browne wrote:
> I'm able to work around the issue by editing GNUmakefile:
> 
> ifeq ($(HAVE_TERMIO_H),True)
> # This termio bit is a grim hack for Solaris 10 (at least).
> # Without it, SGTTY isn't declared.  Something in the ghc C headers
> # which get included before term.h in the generated C is clobbering
> # it.  (If you edit that C and put the curses.h and term.h first, the
> # error goes away.)
> GHCFLAGS_src__Darcs__External.o += '-\#include <termio.h>'
> endif
> 
> After removing this section of the makefile, I'm able to complete the build.

Thanks for the bug report!

When you did your build, did you perform

autoconf
./configure
make

Or did you skip the first couple of steps? Normally skipping the first
couple steps is harmless (because GNUMakefile knows how to do them) but I
can't help but wonder if this could be related.

Also, can you look at your autoconf.make, and see what value it has for
HAVE_TERMIO_H? And could you try (on the clean copy) editing that value
to give it some bogus value (like False), and see if that makes any
difference?

This is a rather puzzling bug.  :( (and thanks again for reporting it!)
-- 
David Roundy
Department of Physics
Oregon State University

David Roundy wrote:

> When you did your build, did you perform
> 
> autoconf
> ./configure
> make
> 
> Or did you skip the first couple of steps? Normally skipping the first
> couple steps is harmless (because GNUMakefile knows how to do them) but I
> can't help but wonder if this could be related.

I ran autoconf, configure, make.

> Also, can you look at your autoconf.make, and see what value it has for
> HAVE_TERMIO_H? And could you try (on the clean copy) editing that value
> to give it some bogus value (like False), and see if that makes any
> difference?

After running autoconf and configure, autoconf.mk contains: 
"HAVE_TERMIO_H   := True".  Thing is, there isn't a termio.h under 
/usr/include, and there isn't one under /opt/local (where MacPorts, the 
dread packaging solution, lives), so True is the bogus value, not False.

I'm not sure what you mean by editing the value on the clean copy. 
Which clean copy of what?

Thanks for your quick reply,

Keith Browne
tuxedo@funkrehab.com

Sorry.  I messed up my fix for HAVE_TERMIO_H in the absence of a
platform without the header.  $ac_cv_header_... has values yes or no
-- I must be getting rusty on autoconf.

I'll send a patch when I figure out why I can't unrecord a version
I've recorded with a bad log message.