X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs Date: Wed, 9 Dec 1998 09:59:14 +0200 (WET) From: Andris Pavenis To: snowball3 AT usa DOT net cc: djgpp-workers AT delorie DOT com Subject: Re: Minor problem building binutils snapshot In-Reply-To: <199812082148.VAA24136@out4.ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com On Tue, 8 Dec 1998 snowball3 AT usa DOT net wrote: > While trying to 'make' the latest weekly binutils snapshot (to test > the patches I submitted), I came across a minor problem. The > make stopped with errors in the file libtool . I stumbled on the > apparent cause of the problem by resaving libtool with editor that > comes with DOS. It turns out the top portion of the generated > libtool files contain CR/LFs for the EOL, but the rest of the file uses > LFs. If I convert the file to either use CR/LFs or LFs, the errors go > away. I had no such problems making the October 8th snapshot. > > I've attached the libtool generated in the opcodes directory so you > can see it for yourselves. The only difference between Oct. 8th and > today is that I'm using the latest djdev202 package and before I > was using the alpha. Is there a setting in bash I can use so libtool > is generated with one or the other? Otherwise, I don't know what to > do. > I have sometimes tried binutils development snapshots for DJGPP when I had problems with exceptions using egcs-1.1 (egcs-1.1.1 fixed these problems). However I choosed different way how to build binutils for DJGPP: cross-compiling under Linux as in such way most MS-DOS related problems go away. Currently I'm using for DJGPP binutils-2.9.1 that I built this way and didn't see problems yet. Such way of course is not nice for releasing DJGPP binaries of some package as requires access to different system and also tools required for cross-compiling. But I think it is Ok for testing purposes. Andris