From: Brian Murphy <brian.murphy@eicon.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: libtool warning on redhat 7.1 native mipsel compile
Date: Tue, 15 Jan 2002 13:57:05 +0100 [thread overview]
Message-ID: <3C442721.76843A70@eicon.com> (raw)
In-Reply-To: 20020114095028.C30946@lucon.org
"H . J . Lu" wrote:
> I should have made myself clearer. I do have X rpms. In fact, my RedHat
> 7.1 mips port has XFree86 4.1 rpms. I just don't use them on my machine.
> I simply can't afford to put X on it. My mips box is used to track gcc
> 3.1, which breaks on Linux/mips almost every week, if not everyday. It
> takes 2 days for me bootstrap/check gcc 3.1 on that box. I need
> something simple to reproduce it.
>
> H.J.
Is it possible for us to help? We have some machines here (Lasat
Masquerade Pro)
which have NEC VR5000 CPU's running at 266 MHz fitted with harddisk and
running
a 2.4.17 kernel. We currently have the debian mips distribution
installed on
them. Perhaps the scripts you use to build/test gcc could be run on one
of
these machines?
/Brian
next prev parent reply other threads:[~2002-01-15 14:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 20:08 libtool warning on redhat 7.1 native mipsel compile Adrian.Hulse
2002-01-11 20:08 ` H . J . Lu
2002-01-12 5:26 ` Ralf Baechle
2002-01-12 5:42 ` H . J . Lu
2002-01-12 5:48 ` Ralf Baechle
2002-01-12 13:36 ` Robin Humble
2002-01-12 17:22 ` H . J . Lu
2002-01-13 4:04 ` Robin Humble
2002-01-13 6:27 ` H . J . Lu
2002-01-14 11:44 ` Maciej W. Rozycki
2002-01-14 17:50 ` H . J . Lu
2002-01-15 12:57 ` Brian Murphy [this message]
2002-01-15 15:46 ` H . J . Lu
2002-01-14 11:35 ` Maciej W. Rozycki
2002-01-14 17:56 ` H . J . Lu
-- strict thread matches above, loose matches on Subject: below --
2002-01-11 19:53 Adrian.Hulse
2002-01-11 19:56 ` H . J . Lu
2002-01-11 20:12 ` Maciej W. Rozycki
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=3C442721.76843A70@eicon.com \
--to=brian.murphy@eicon.com \
--cc=linux-mips@oss.sgi.com \
/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