: [EMAIL PROTECTED]
Cc: Arek; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Problems upgrading from 2.95.3-5 to 3.X on cygwin
On Feb 3, 2002, Tim Prince <[EMAIL PROTECTED]> wrote:
> a build of libgcj, and then tried to correct it by running configure again,
> you must delete the c
On Feb 3, 2002, Tim Prince <[EMAIL PROTECTED]> wrote:
> a build of libgcj, and then tried to correct it by running configure again,
> you must delete the corresponding build subdirectories. I do wonder why
> cygwin is not among the targets which have workable configure defaults.
Because nobo
On Saturday 02 February 2002 13:02, Arek wrote:
> 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-bu
To: "Mack Lobell" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
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 usin
-
From: Neil Booth [mailto:[EMAIL PROTECTED]]
Sent: Saturday, 2 February 2002 9:05
To: Mack Lobell
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
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
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 st
6 matches
Mail list logo
