From: "H . J . Lu" <hjl@lucon.org>
To: 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 07:46:52 -0800 [thread overview]
Message-ID: <20020115074652.A18875@lucon.org> (raw)
In-Reply-To: <3C442721.76843A70@eicon.com>; from brian.murphy@eicon.com on Tue, Jan 15, 2002 at 01:57:05PM +0100
On Tue, Jan 15, 2002 at 01:57:05PM +0100, Brian Murphy wrote:
> "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?
If you have some spare mips machines and want to help, you can check
out the gcc main trunk from CVS:
http://gcc.gnu.org/
You can build/check it and send in the test result. It has to be done
continuously since any checkin can break gcc on Linux/mips. You can
also check out glibc from CVS:
http://sources.redhat.com
and build/check it. The failed glibc tests should be sent to the glibc
mailing list.
H.J.
next prev parent reply other threads:[~2002-01-15 16:46 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
2002-01-15 15:46 ` H . J . Lu [this message]
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=20020115074652.A18875@lucon.org \
--to=hjl@lucon.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.