All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Jun Sun <jsun@mvista.com>,
	ralf@oss.sgi.com, vhouten@kpn.com, linux-mips@oss.sgi.com
Subject: Re: Updates on RedHat 7.1/mips
Date: Tue, 17 Jul 2001 21:16:05 +0200	[thread overview]
Message-ID: <3B548EF5.993C271E@mips.com> (raw)
In-Reply-To: 20010716142802.A2757@lucon.org

"H . J . Lu" wrote:

> On Mon, Jul 16, 2001 at 01:26:32PM +0200, Carsten Langgaard wrote:
> > "H . J . Lu" wrote:
> > > > Now I would like to try to install H.J. Lu's RedHat7.1 RPM packages.
> > > > If I just do a:
> > > >     rpm -Uvh --root /mnt/harddisk *.rpm
> > >
> > > Those rpms have to be installed in the right order. I have a set up
> > > to do that. I will see what I can do.
> >
> > Thanks, please do.
>
> They are in install.tar.bz2 now.

Thanks a lot, that look like something we have been needing for a long time

> > Another thing, I can see your distribution is lacking kernel header
> > files, I guess they are needed to do a native compile of the source RPMs.
>
> I added gdb and kernel-headers. I also updated gcc, glibc and binutils.
> The toolchain rpms are updated.

Now that I'm at it :-)
Could you add a Perl rpm to you distribution, this also seems to be needed to
build the RPMs natively.

I also would like to do a cross build, but how do I do that ?
Do I have to change all the spec files, to set the target arch to MIPS, or is
there a easier and better way to do that ?
I guess if I just install the SRPMs and the cross toolchain, and try to build
out of that I will simply build for the build platform, which is i386.

>
>
> H.J.
> ------
> My mini-port of RedHat 7.1 is at
>
> ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/
>
> you should be able to put a small RedHat 7.1 on the mips/mipsel box and
> compile the rest of RedHat 7.1 yourselves.
>
> Here are something you should know:
>
> 1. The cross compiler hosted on RedHat 7.1/ia32 is provided as a
> toolchain rpm. The binary rpms for the mips and mipsel cross compilers
> are included. You will need glibc 2.2.3-11 or above to use those
> rpms. The glibc x86 binary rpms under RPMS/i386 should be ok.
> 2. You have to find a way to put those rpms on your machine. I use
> network boot and NFS root to do it.
> 3. install.tar.bz2 has some scripts to prepare NFS root and install
> RedHat 7.1 on a hard drive.
>
> Thanks.
>
> H.J.

  reply	other threads:[~2001-07-17 19:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-06  8:15 Illegal instruction Carsten Langgaard
2001-07-06  9:27 ` Houten K.H.C. van (Karel)
2001-07-06 11:42   ` Maciej W. Rozycki
2001-07-06 13:26 ` Dan Aizenstros
2001-07-06 22:04 ` Jun Sun
2001-07-10 11:14   ` Carsten Langgaard
2001-07-10 17:31     ` H . J . Lu
2001-07-16 11:26       ` Carsten Langgaard
2001-07-16 21:28         ` Updates on RedHat 7.1/mips H . J . Lu
2001-07-17 19:16           ` Carsten Langgaard [this message]
2001-07-17 19:29             ` H . J . Lu
2001-07-17 19:50               ` Daniel Jacobowitz
2001-07-17 19:57                 ` H . J . Lu
2001-07-17 20:09                   ` Ilya Volynets
2001-07-17 20:11                     ` H . J . Lu
2001-07-18  3:52                       ` Arnaldo Carvalho de Melo
2001-07-18  4:01                         ` Ilya Volynets
2001-07-18  7:13               ` Carsten Langgaard
2001-07-18 15:11                 ` H . J . Lu
2001-07-18 15:23                   ` Carsten Langgaard
2001-07-18 20:53                     ` Seth Mos
2001-07-19  0:36                       ` H . J . Lu
2001-07-19 21:03                         ` Seth Mos
  -- strict thread matches above, loose matches on Subject: below --
2001-07-18 12:07 Gleb O. Raiko
2001-07-18 13:26 Ralf Baechle
2001-07-18 16:48 ` Daniel Jacobowitz
2001-07-18 22:23   ` Ralf Baechle
2001-07-19 13:29     ` Florian Lohoff

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=3B548EF5.993C271E@mips.com \
    --to=carstenl@mips.com \
    --cc=hjl@lucon.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=vhouten@kpn.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.