Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	Peter Dufault <dufault AT hda DOT com>
Message-Id:	<200001041553.KAA16957@hda.hda.com>
Subject:	cygwin,wine,freebsd: Summary
To:	cygwin AT sourceware DOT cygnus DOT com
Date:	Tue, 4 Jan 2000 10:53:36 -0500 (EST)
X-Mailer:	ELM [version 2.4ME+ PL43 (25)]
MIME-Version:	1.0

OK, I've finished what I have to do.  I can now cross-build the .EXE
files on FreeBSD using the same tools the end customer will use,
and test simple .EXEs under wine.  

FreeBSD 3.3, Wine patches
cygwin b20.1
wine wine-991212

Bootstrapping host tools:

../src/configure --prefix=/usr/local/cygb20.1 --target=i586-cygwin32 -v

There are two problems in this part.

The first is that when building "diff"
HAVE_SETMODE configures in and calls the 4.4 setmode which has
a different number of arguments.  I'm not good with the configure,
so I took out the bootstrap of "diff" since I don't need it.

The second is that the install in winsupp keeps wiping out /dev/null,
I assume by "creat"ing it.

I changed the install to this:

--- ./cygwin-b20.1/src/winsup/Makefile.in.orig	Mon Nov 30 20:42:31 1998
+++ ./cygwin-b20.1/src/winsup/Makefile.in	Mon Jan  3 14:50:09 2000
@@ -334,7 +334,7 @@
 
 new-$(DLL_NAME): $(DLL_OFILES) $(DEF_FILE) $(DLL_IMPORTS) $(LIBC_A) $(LIBM_A) Makefile version.o
-	$(LD) --base-file=cygwin.base -s -o /dev/null $(LD_STUFF)
+	$(LD) --base-file=cygwin.base -s -o - > /dev/null $(LD_STUFF)
 	$(DLLTOOL) $(DLL_STUFF)
-	$(LD) --base-file=cygwin.base cygwin.exp -s -o /dev/null $(LD_STUFF)
+	$(LD) --base-file=cygwin.base cygwin.exp -s -o - > /dev/null $(LD_STUFF)
 	$(DLLTOOL) $(DLL_STUFF)
 	$(LD) cygwin.exp -o new-$(DLL_NAME) $(LD_STUFF)

Now you can build and install the bootstrap tools.  To investigate
Wine you can then build the native tools with this configuration:

../src/configure \
	--prefix=/usr/local/cygb20.1 \
    	--exec-prefix=/usr/local/cygb20.1/i586-cygwin32 \
    	--target=i586-cygwin32 --host=i586-cygwin32 \
    	--build=i386-unknown-freebsd3.3 -v

As I mentioned earlier, there is then a problem of determining
when something is a console.  This is a Wine problem,
however, I hacked around it hinfo.cc.
Now I can run simple programs.  All further work I'll persue in the Wine
world by trying to fix the console detection and handling of relocatable
binaries.

Peter

-- 
Peter Dufault (dufault AT hda DOT com)   Realtime development, Machine control,
HD Associates, Inc.               Safety critical systems, Agency approval

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -