Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Dario Alcocer <alcocer AT helixdigital DOT com>
MIME-Version:	1.0
Message-ID:	<15092.3994.736535.680896@coyote.priv.helixdigital.com>
Date:	Sat, 5 May 2001 07:35:06 -0700
To:	cygwin AT cygwin DOT com
Subject:	PATCH: Updated build instructions for cygwin1.dll
X-Mailer:	VM 6.76 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid

--cK5PMdsm5j
Content-Type: text/plain; charset=us-ascii
Content-Description: message body text
Content-Transfer-Encoding: 7bit

A few days back I read the following message from Chris Faylor
regarding the correct build procedure for the cygwin1.dll:

    http://cygwin.com/ml/cygwin/2001-04/msg00712.html

Since I believe these instructions are more detailed, I'd like to
submit the attached patch for how-programming.texinfo to bring the
build instructions in the FAQ up-to-date.

Comments?


--cK5PMdsm5j
Content-Type: text/plain
Content-Description: PATCH: Updated cygwin1.dll build instruction
Content-Disposition: inline;
	filename="cygwin-faq-rebuild.patch"
Content-Transfer-Encoding: 7bit

--- ./winsup/doc/how-programming.texinfo.orig	Tue Oct 31 08:58:09 2000
+++ ./winsup/doc/how-programming.texinfo	Sat May  5 07:19:00 2001
@@ -170,15 +170,25 @@
 @strong{Note:} You must build in a directory @emph{outside} the source
 tree.
 
-Assuming that you have the src installed as /src, will build in
-the directory /obj, and want to install the tools in /install:
+The Cygwin DLL follows the same @samp{./configure; make; make install}
+mechanism GNU tools use for building.  The difference is that, unlike
+building a GNU package, care must be taken not to clobber the Cygwin DLL
+that's being is being used during the build.  The way this is
+accomplished is by specifying additional macro definitions when running
+@samp{make install} not usually required when building GNU tools.
+
+The correct procedure is as follows, assuming you're building in /obj,
+the Cygwin DLL sources have been unpacked in /src, and your finished
+Cygwin environment get installed into /netrel/inst:
 
 @example
-bash
 cd /obj
-/src/configure --prefix=/install -v > configure.log 2>&1
-make > make.log 2>&1
-make install > install.log 2>&1
+/src/configure --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc \
+    --libdir=/usr/lib --libexecdir=/usr/sbin
+make
+make prefix=/netrel/inst/usr exec_prefix=/netrel/inst/usr \ 
+     sysconfdir=/netrel/inst/etc libdir=/netrel/inst/usr/lib \ 
+     libexecdir=/netrel/inst/usr/sbin install
 @end example
 
 Normally, this will also attempt to build the documentation, which

--cK5PMdsm5j
Content-Type: text/plain; charset=us-ascii
Content-Description: .signature
Content-Transfer-Encoding: 7bit


-- 
Dario Alcocer -- Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.com


--cK5PMdsm5j
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
--cK5PMdsm5j--

- Raw text -