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: Date: Fri, 1 Jul 2005 10:59:13 -0400 From: Tony Karakashian Reply-To: Tony Karakashian To: cygwin AT cygwin DOT com Subject: Re: Cygwin from Scratch? In-Reply-To: <42C557FF.3020507@familiehaase.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42C464B0 DOT C8D5A7AE AT dessent DOT net> <42C557FF DOT 3020507 AT familiehaase DOT de> X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j61ExLtj027034 > 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;) Hehehe, precisely what I do, too. I figure they've generally hammered out most of the rough edges. Heck, if for no other reason than you get a list of everything that needs to be installed before you can assemble a package, it's a godsend. > BTW, do you know which was the last version of gcc which could be build > without having gcc already handy? Honestly, no. Been a while since I built an LFS. I've pretty much given up on Linux in general, so that's why I've been concentrating on Cygwin... -T -- 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/