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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <001401c1ac2c$dfe74a20$0700a8c0@vergenet.com> From: "Arek" To: , References: <8D00C32549556B4E977F81DBC24E985D410215 AT crtsmail1 DOT technol_exch DOT corp DOT riotinto DOT org> Subject: Re: Problems upgrading from 2.95.3-5 to 3.X on cygwin Date: Sat, 2 Feb 2002 15:02:06 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Okay, On a whim, I decided to upgrade to GCC 3.0.3 on my box. Following David Billinghurst's instructions, everything went fine until 'make install', where it failed with the following error: make[1]: Entering directory `/home/james/gcc-build/fastjar' make[2]: Entering directory `/home/james/gcc-build/fastjar' /bin/sh ../../gcc-3.0.3/fastjar/mkinstalldirs /usr/local/bin /bin/sh /home/james/gcc-3.0.3/install-sh -c jar /usr/local/bin/jar chmod: changing permissions of `/usr/local/bin/#inst.328557#': No such file or d irectory make[2]: *** [install-binPROGRAMS] Error 1 make[2]: Leaving directory `/home/james/gcc-build/fastjar' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/home/james/gcc-build/fastjar' make: *** [install-fastjar] Error 2 james AT JAMES ~/gcc-build $ After doing a little investigating, I found out that it's trying to chmod `/usr/local/bin/#inst.328557#' instead of `/usr/local/bin/#inst.328557#.exe'. Any idea what might be causing this? Thanks in advance. James Potts (james AT verge-rpg DOT com) ----- Original Message ----- From: "Billinghurst, David (CRTS)" To: "Mack Lobell" Cc: ; Sent: Friday, February 01, 2002 4:57 PM Subject: RE: Problems upgrading from 2.95.3-5 to 3.X on cygwin > Mack, > > A couple of things to try: > > Unpack the gcc source tree using cygwin tar and gzip/bzip2. Some windows utilities are "smart" enough to convert \n to \r\n > > Try using binary mounts for the source and build trees. > > Use the configure options I posted earlier. > > -----Original Message----- > From: Neil Booth [mailto:neil AT daikokuya DOT demon DOT co DOT uk] > Sent: Saturday, 2 February 2002 9:05 > To: Mack Lobell > Cc: cygwin AT cygwin DOT com; gcc AT gcc DOT gnu DOT org > Subject: Re: Problems upgrading from 2.95.3-5 to 3.X on cygwin > > > I suggest you remove all '\r' characters from i386.md, so that the > newlines consist of '\n' only. That will likely solve your problem. > > You needn't bother with insn-flags.h; that looks to be only a warning > and once you get stage1 built of 3.0, it won't have problems with > '\r' (but the .md file still might; I'm not sure about that). > > Neil. > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/