From: Tudor Hulubei <tudor.hulubei@ecora.com>
To: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
Cc: gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: gcc-2.95.2 on the Cobalt Qube2
Date: Thu, 17 Feb 2000 15:02:00 -0000 [thread overview]
Message-ID: <14508.32183.418750.321658@data.ecora.com> (raw)
In-Reply-To: <200002172236.XAA01873@loewis.home.cs.tu-berlin.de>
On Thursday, 17 February 2000, Martin v. Loewis wrote:
> > Are there any plans on porting 2.95.2 to the Cobalt Qube2? Cobalt
> > provides egcs-1.0.2, which is pretty old. egcs-1.1.2 works (kind
> > of), but I couldn't get 2.95.2 to work. Is there a patch for 2.95.2
> > for mips/Qube2?
>
> Did you report the problems you are seeing? I don't think anybody has
> explicit plans to support these systems, except potentially for owners
> of them. I'd guess Cobalt may also be able to help.
Actually, I've just made another attempt at compiling gcc-2.95.2 on
the Cobalt Qube2, by applying some of the patches that were
distributed by Cobalt. It seems to work ok so far (although the
installation wasn't smooth). I can provide further info, if there is
interest.
Tudor
WARNING: multiple messages have this Message-ID
From: Tudor Hulubei <tudor.hulubei@ecora.com>
To: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
Cc: gcc@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: gcc-2.95.2 on the Cobalt Qube2
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <14508.32183.418750.321658@data.ecora.com> (raw)
Message-ID: <20000401000000.dZi8EmPHUQf17VT2KDN8Bqie3UAgSDCydbKP80jloFg@z> (raw)
In-Reply-To: <200002172236.XAA01873@loewis.home.cs.tu-berlin.de>
On Thursday, 17 February 2000, Martin v. Loewis wrote:
> > Are there any plans on porting 2.95.2 to the Cobalt Qube2? Cobalt
> > provides egcs-1.0.2, which is pretty old. egcs-1.1.2 works (kind
> > of), but I couldn't get 2.95.2 to work. Is there a patch for 2.95.2
> > for mips/Qube2?
>
> Did you report the problems you are seeing? I don't think anybody has
> explicit plans to support these systems, except potentially for owners
> of them. I'd guess Cobalt may also be able to help.
Actually, I've just made another attempt at compiling gcc-2.95.2 on
the Cobalt Qube2, by applying some of the patches that were
distributed by Cobalt. It seems to work ok so far (although the
installation wasn't smooth). I can provide further info, if there is
interest.
Tudor
next prev parent reply other threads:[~2000-02-17 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-17 0:32 Tudor Hulubei
2000-02-17 14:42 ` Martin v. Loewis
2000-02-17 15:02 ` Tudor Hulubei [this message]
2000-02-17 15:08 ` Tudor Hulubei
2000-04-01 0:00 ` Tudor Hulubei
2000-04-01 0:00 ` Tudor Hulubei
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Tudor Hulubei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14508.32183.418750.321658@data.ecora.com \
--to=tudor.hulubei@ecora.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=martin@loewis.home.cs.tu-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).