From:	N8TM AT aol DOT com
Subject:	Re: b20.1: build question
31 Dec 1998 09:24:15 -0800 :
Message-ID:	<a92368f9.368b3321.cygnus.gnu-win32@aol.com>
Mime-Version:	1.0
To:	kevins AT citrix DOT com, gnu-win32 AT cygnus DOT com

In a message dated 12/30/98 9:49:54 PM Pacific Standard Time,
kevins AT citrix DOT com writes:

<< On my NT4.0 box, should I be able to:
 
 1.  Download dev-src_tar.b2
 2.  Uncompress and untar it.
 3.  From a new obj directory, type 'configure --host=i586-pc-cygwin32
 --prefix=/install'
 3a. Muck about with the newlib configuration to get it to work.
 4.  Do a 'make'
 5.  Drop the obj/i586-pc-cygwin32/winsup/new-cygwin1.dll into my current
 toolset?
 
 This doesn't seem to work -- I get access violations immediately.  Is this
 supposed to
 work?  Or, do I have to build everything from the same source with the same
 compiler?
 
 Also, I was unable to do a 'make install' which failed during gcc
 installation.
 
 Any clues?
  >>
I rebuilt b20.1 onto itself on W95, using a working make-3.77 running on
B19/coolview.  I don't recall whether b20.1 is able to build make-3.77
directly on NT (I'm on vacation).  If so, you might try that.  If not, it
confirms that the make binary is inadequate.  'make install' in make-3.77 is
not cygwin-compatible unless you have one of those special install programs
which deal with .exe without requiring .exe support in the install script.  

'make install' of b20.1 of course will fail at the points where install is
trying to replace its copy of cygwin1.dll and make.exe if you are running the
installed one, but  make -k install runs for me and skips only the
replacements of the files which are in use.  I ran 'make -k install' twice,
both in b19 (with b20.1 not running) and in b20.1, but I think you can do
without b19.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -