Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42C557FF.3020507@familiehaase.de> Date: Fri, 01 Jul 2005 16:49:35 +0200 From: "Gerrit P. Haase" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin from Scratch? References: <42C464B0 DOT C8D5A7AE AT dessent DOT net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Tony Karakashian wrote: > Fortunately, most of the hard work has been done for existing > packages. A CFS "book" would simply require compiling instructions in > one place as well as patches, etc. Could be a fun project. Basically I do nothing but building from scratch. That is the reason why I became maintainer for several packages. However, I'm lazy and have not enough spare time to always build a package when there is an update available, so I appreciate that there are other maniacs doing the same. I use official Cygwin builds to build release packages, though. If there are problems building a new package, the first resource is LFS or BLFS of course, what else? So besides LFS is missing some basic Cygwin packages it is already the best guide available when building new packages. Just rename it;) BTW, do you know which was the last version of gcc which could be build without having gcc already handy? Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/