[prev in list] [next in list] [prev in thread] [next in thread] 

List:       autoconf-bug
Subject:    Re: Report this to bug-autoconf@gnu.org
From:       Ralf Wildenhues <Ralf.Wildenhues () gmx ! de>
Date:       2007-05-10 6:59:20
Message-ID: 20070510065920.GC10984 () ins ! uni-bonn ! de
[Download RAW message or body]

Hello Marek,

Thanks for the report.

* Marek Burza wrote on Wed, May 09, 2007 at 05:57:45PM CEST:
>
> I was trying to install an extension (network-2.0) to Haskell on cygwin
> and I got an error or warning which requested to be reported to you :)
> You can see the output below and if you need more info I'll be glad to
> provide it to you.
[...]

> checking winsock.h usability... no
> checking winsock.h presence... yes
> configure: WARNING: winsock.h: present but cannot be compiled
> configure: WARNING: winsock.h: check for missing prerequisite headers?
> configure: WARNING: winsock.h: proceeding with the preprocessor's result
> configure: WARNING:     ## ------------------------------------ ##
> configure: WARNING:     ## Report this to bug-autoconf@gnu.org. ##
> configure: WARNING:     ## ------------------------------------ ##
> checking for winsock.h... yes
[...]

Please read
  http://www.gnu.org/software/autoconf/manual/html_node/Present-But-Cannot-Be-Compiled.html

and then show that to the maintainer of the Haskell package, who can
fix this in his package.  The error becomes clearer if you look at the
part of the config.log file that deals with this compile failure (and
maybe also some Cygwin documentation).

> nlv13536@NLVEHVRES2DT1C9 $ runghc Setup.hs build
> Preprocessing library network-2.0...
> Building network-2.0...
> cbits\ancilData.c: In function `sendFd':
>
> cbits\ancilData.c:47:0:
>     error: variable `msg' has initializer but incomplete type
[...]

FWIW, these may or may not be followup errors; I don't know.

Cheers,
Ralf



[prev in list] [next in list] [prev in thread] [next in thread]