Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 4 Jun 2002 01:01:01 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Building cygwin1.dll and mknetrel
Message-ID: <20020604050101.GA12031@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020528120346 DOT B21064 AT monster DOT rich-paul DOT net> <4 DOT 3 DOT 1 DOT 2 DOT 20020528122339 DOT 0260f7f0 AT pop DOT ma DOT ultranet DOT com> <20020528190238 DOT A22088 AT monster DOT rich-paul DOT net> <20020528232930 DOT GA18281 AT redhat DOT com> <20020529091728 DOT D22088 AT monster DOT rich-paul DOT net> <20020529143618 DOT GA2808 AT redhat DOT com> <20020602004747 DOT A10315 AT monster DOT rich-paul DOT net> <20020602062824 DOT GA1808 AT redhat DOT com> <20020602072107 DOT B10865 AT monster DOT rich-paul DOT net> <20020603053325 DOT A13720 AT monster DOT rich-paul DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020603053325.A13720@monster.rich-paul.net>
User-Agent: Mutt/1.3.23.1i

On Mon, Jun 03, 2002 at 05:33:25AM -0400, linguist-cygwin AT rich-paul DOT net wrote:
>	*	mknetrel, it appears, can build most but not all cygwin
>	 	packages.  vim, for example, looses, because the build must be
>		done in the src directory.  It looks like an 'extras' script
>		could be produced to accomidate vim, either with a link tree (I
>		seem to recall the vim build supports this) or some other hack.

mknetrel is, AFAIK, only used by myself for producing net release packages.  Egor
Duda has obviously been experimenting with it (possibly for use in building gcc)
but he doesn't use it for package maintenance yet, AFAIK.

>	*	On my production system, I had to change the '#!/bin/sh' to
>		'#!/bin/bash' on one of the mknetrel shell scripts
>		to get the shell to accept the usage of getopts ... but on the
>		fresh install, I did not.  (This is the bash getopts builtin,
>		not the standalone and singular 'getopt' discussed above)

Yes, I have never run this under cygwin, actually.  It was intended as a
cross-compilation environment.  I'm surprised that it works on cygwin
with so few changes.

>	*	The fact that mknetrel uses i686-pc-cygwin-xxx as it's tools
>		during the build implies that it may work with a cross compiler
>		as well, or may have been developed to cross compile.  I haven't
>		yet had time to prove this.

Yep.

>	*	I use wildcards in some places to avoid explicitly stating
>		package versions.  The drawback to this approach is that it will
>		break in the presence of dup package versions.

You should be able to say "mknetrel cygwin" to have it build the latest version.
Again, I'm surprised that it would actually work with explicit versions.

>	*	Some of my test builds produced a linux version of libiberty as
>		an added bonus.  I don't know why, but it didn't seem to hurt
>		anything

"That's the way it works" (tm)

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/