On Thu, 9 Nov 2000, Andrew Lynch wrote:
[...]
> Cygwin does not provide glibc. It uses newlib
> instead, which
> provides much (but not all) of the same functionality.
> Porting glibc
> to Cygwin would be difficult.
Ok. I don't know how much problem this will cause. The other thing I
thought about is the threading issue: Wine uses the platform's low-level
threads. This is platform specific and thus different on Linux, Solaris
and BSD (see the current wine-dev thread about Solaris 8). What kind of
low-level thread primitive do they offer in cygwin?
With any louck it will be similar to what's in FreeBSD. Again you'll
see when you get there.
[...]
> tarball to make a fresh build. I commented out the
> original lines changed, made changes that Alexandre
> Julliard suggested to configure.in, and reran the
> ./tools/wineinstall as before. The make file log is
> attached.
Did you rerun autoconf after modifying configure.in?
Explanation:
There's two files: 'configure' and 'configure.in'.
What wineinstall runs is 'configure'. 'configure' is generated from
the 'configure/in' files by autoconf. So usually after modifying the
configure.in file one runs autoconf to update the configure script, and
then you run the configure script (or wineinstall).
From what you say it sounds like you modified configure.in but not
configure. When the changes are so simple, you can do the changes
directly in the configure script, especially if you don't have autoconf
available.
--
Francois Gouget [EMAIL PROTECTED] http://fgouget.free.fr/
The nice thing about meditation is that it makes doing nothing quite respectable
-- Paul Dean
