Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: Date: Sat, 2 Jul 2005 10:38:09 -0700 From: Joshua Daniel Franklin Reply-To: Joshua Daniel Franklin To: cygwin@cygwin.com Subject: Re: Cygwin from Scratch? In-Reply-To: <42C4671C.E390CD15@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42C464B0.C8D5A7AE@dessent.net> <42C4671C.E390CD15@dessent.net> X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j62HcIvl017189 > Brian Dessent wrote: > > > In my experience the two most common changes you have to make when > > porting are: a) adding -no-undefined to LDFLAGS (or -Wl,-no-undefined to > > CFLAGS), and b) adding missing $(EXEEXT) ... > > I meant to include c) adding O_BINARY to open() or otherwise dealing > with textmode/binmode issues. Would these be good to add to the "Making Pakcages" list? http://cygwin.com/setup.html#package_contents -- 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/