The issue is just that there is no defined configuration for cygnus.
I followed the install directions...e.g.
cd into the arch directory and do either config.bat or ./configure.
Neither worked for any of the platforms in the directory.
What exactly did you do to build on your windows machine?
There is no cygwin arch directory in the distribution available for
download.
I have not tried to build the June release.
I am downloadintg CygWinb20 now so I can build the java bridge I
described to the list (I had been using b19).
I will take a shot at building hugs as well. Just tell me what the build
instructions are.
As far as unix, it was just the arch that I thought most closely matched
my config. e.g. cygwinb19 w/ tcsh as my shell.
-Alex-
On Fri, 13 Nov 1998, Mark P Jones wrote:
> | I took a shot at building this on cygwin w/ egcs and it failed.
> | Neither the unix build nor the dgjpp build would take.
> | I don't have borland or microsoft c compilers installed.
>
> Most puzzling. Before making the release available, I built and tested
> it on all of the platforms at my disposal:
>
> unix (Solaris)
> djgpp2
> msc (Microsoft Visual C++ version 5 on NT4)
> msc (Microsoft Visual C++ version 6 on Win98)
> bcc32 (Borland C++ 4.52 on Win98 and NT4)
> win32 (Borland C++ 4.52 on Win98 and NT4)
>
> All of these built *without* problem. Prompted by your message,
> I downloaded and installed a copy of cygwin-b20 under NT4 this morning.
> I'm a first time cygwin user, but again I had no problem building Hugs.
>
> In other words, I've built Hugs 981111 on all the platforms that you
> mentioned, without any problems. I've also heard from Hans Aberg,
> who has built a copy on the mac (ftp://haskell.org/pub/incoming/MacHugs).
>
> Perhaps there is something strange about your particular configuration.
> For example:
>
> | Btw, the unix build error messages were:
> | ...
> | In file included from hugs.c:20:
> | C:\TOOLS\CYGNUS\B19\H-I386~1\lib\gcc-lib\i386-cygwin32\egcs-2.90.2
> | 7\../../../../i386-cygwin32/include/ctype.h:62: warning:
> | `isascii' redefined
> | ...
>
> If this is really was a Unix build, then I'm surprised to see a filename
> that includes components like "C:\", "H-I386~1", and "i-386-cygwin32",
> all of which suggest *Windows*. Was this a typo? Is the confusion
> here perhaps the source of the problems you've been having? I'd also
> be interested to hear whether you experience similar problems if you
> attempt to build the Hugs-June98 release on your machine. Things haven't
> changed too much in this part of the system, so if you can do one, then
> you should be able to do the other. Let me know how you get on, or if
> you can supply more information that will allow me to reproduce the
> problems that you've described.
>
> All the best,
> Mark
>
___________________________________________________________________
S. Alexander Jacobson i2x Media
1-212-697-0184 voice 1-212-697-1427 fax
