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 From: "Dave Korn" To: Subject: RE: Link problem when building cygwin1.dll (parsing cygwin.def) Date: Wed, 27 Jul 2005 16:56:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050727153831.GE31984@trixie.casa.cgf.cx> Message-ID: ----Original Message---- >From: Christopher Faylor >Sent: 27 July 2005 16:39 > On Wed, Jul 27, 2005 at 04:25:37PM +0100, Dave Korn wrote: >> ----Original Message---- >>> From: Eitan Eliahu >>> Sent: 27 July 2005 15:47 >> >>> Dave, attached is the def file after I ran d2u on it. >> >> It still has \r\n line ends. > > I don't see them in the file that he attached. I do; one of our mailers must have done some translation. FWIW, I used Outlook and dragged-and-dropped the attachment into an explorer window, then brought up bash in the same window and ran od, and there were CRLFs in the resulting file. I guess it's quite likely to be Outlook trying to be clever. >I do see a lot of these > types of lines, though: > > LIBRARY "cygwin1.dll" BASE=0x61000000 > > EXPORTS > = _sigfe_ > = _sigfe_ > = _sigfe_ > = _sigfe_ > > which are, presumably, where the error is coming from. I can't explain > what's causing them, however. CRLF-terminated lines in sigfe.s? I still think checking out a new, guaranteed-uncontaminated-by-DOSisms CVS tree is the next thing to try. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/