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
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C0F9761.1040304@ece.gatech.edu>
Date: Thu, 06 Dec 2001 11:05:53 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jan Nieuwenhuizen <janneke AT gnu DOT org>
CC: "Gerrit P. Haase" <cygwin AT cygwin DOT com>
Subject: Re: experimental texmf packages
References: <m3bshtmxhb DOT fsf AT appel DOT lilypond DOT org>	<878764062 DOT 20011128173421 AT nyckelpiga DOT de>	<m37ks9lgxi DOT fsf AT appel DOT lilypond DOT org>	<4434079433 DOT 20011129221637 AT familiehaase DOT de>	<m3oflgy98n DOT fsf AT appel DOT lilypond DOT org>	<9517228633 DOT 20011203135833 AT familiehaase DOT de>	<m3lmgkwgeu DOT fsf AT appel DOT lilypond DOT org> <3C0D8535 DOT D67735D1 AT ece DOT gatech DOT edu>	<m33d2pam3l DOT fsf AT appel DOT lilypond DOT org> <3C0EAD6B DOT AD71A7EB AT ece DOT gatech DOT edu> <m3bshc3ejt DOT fsf AT appel DOT lilypond DOT org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

Jan Nieuwenhuizen wrote:

> 
> Ok thanks for the pointer.  Is there a script to do the packaging?


yep -- each script contains a script (in some package schemes -- #3, I 
think -- you have to apply the patch FIRST, and then the script is 
created in <srcdir>/CYGWIN-PATCHES/ or something).


>>pop quiz: what are the current configure flags used to build gcc? 
>>Anyone?  Anyone?  Bueller? (no, Chris, you're not allowed to answer..)
>>
> 
>    That's easy:
> 
> What do I win?


No, no, no.  Not "What flags does Jan use" but "What flags WERE used to 
build the official cygwin gcc package".  (Hint: only cgf knows for sure)


> Ok.  Although my scripts have run a bit out of hand, my autobuilds run
> rather well now.  They will only get simpler when packages are
> packaged more cleanly.


Mine too.


> Ok.  So you're still aiming for a lot less ambitious target.  This
> just means that I'll have to hack up some scripts to do cross
> building, as none of them will support it.  


Yep -- you'll have to edit the line where it says "host=i686-pc-cygwin" 
and change it to something appropriate.

> Anyway, documentation in
> the form of a script is a very good start, I guess.
> 
> Ok, I didn't know that.  Feb 1999 I sent this mail:
> 
>     http://www.cygwin.com/ml/cygwin/1999-02/msg00822.html

...

> Sure, but it was skipped over when I announced it, ie b20 was current,
> too.
 

Ah, but back in b20 days we didn't HAVE package-based distribution. 
Everything was all in one "full.exe" 21MB download. There was no way for 
a non-core developer to add something like "rpm" to the distro back then 
-- it just wasn't possible.  A lot of things have changed in 3 years.

--Chuck







--
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/