Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Mike McDonald <mikemac@mikemac.com>
To: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross compiling RPMs
Date: Sat, 27 Jan 2001 14:57:24 -0800	[thread overview]
Message-ID: <200101272257.OAA05689@saturn.mikemac.com> (raw)
In-Reply-To: Your message of "Sat, 27 Jan 2001 11:52:05 +0100." <200101271052.LAA21268@sparta.research.kpn.com>


>Date: Sat, 27 Jan 2001 11:52:05 +0100 (MET)
>From: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
>Subject: Re: Cross compiling RPMs
>To: mikemac@mikemac.com (Mike McDonald)
>
>Mike wrote:
>> 
>>   If one were to go the native compiling route, what would the minimum
>> set of rpms needed be? kernel, bin-utils, cc. file-utils? ???
>> 
>
>It depends on what and how you want to compile. To use rpm, you need
>quite a lot tools (db3, patch, sed, grep, find,...). Beside that
>you'll at least need glibc, binutils, gcc, and make. But you'll find
>out that you'll have to compile flex, bison, m4, automake, autoconf,
>and even perl to get rpm builds going. My mipsel native environment
>currently has the following packages:

  I was thinking of what the MINIMUM set of RPMs you needed installed
so you could bootstrap a system up from sources, not what's the
minimum needed to recompile any arbitrary RPM.

>But you surely can start with less... :-)

  With less than 150 files installed in a root file system, I can
install the bin-utils, gcc, make, and glibc RPMs. From there, I should
be able to begin cross compiling the other basic RPMs for a system.
That's my ultimate goal.

  Mike McDonald
  mikemac@mikemac.com

  parent reply	other threads:[~2001-01-27 22:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 18:15 Cross compiling RPMs Mike McDonald
2001-01-26 18:37 ` Pete Popov
2001-01-26 19:27   ` Mike McDonald
2001-01-26 19:39     ` Pete Popov
2001-01-26 19:47       ` Mike McDonald
2001-01-26 20:23   ` Florian Lohoff
2001-01-26 20:51     ` Jun Sun
2001-01-26 21:11       ` Mike McDonald
2001-01-27  0:31         ` Pete Popov
2001-01-26 21:14     ` Mike McDonald
2001-01-27 10:52       ` Karel van Houten
2001-01-27 10:52         ` Karel van Houten
2001-01-27 22:57         ` Mike McDonald [this message]
2001-01-28 12:10           ` Ralf Baechle
2001-01-28 17:45             ` Mike McDonald
2001-01-29  0:05               ` Ralf Baechle
2001-01-29 15:23               ` Maciej W. Rozycki
2001-01-27  7:42     ` Maciej W. Rozycki
2001-01-27 18:50       ` Ralf Baechle
2001-01-28 18:30         ` Geert Uytterhoeven
2001-01-28 19:46           ` Pim van Riezen
2001-01-28 19:46             ` Pim van Riezen
2001-01-29  0:02           ` Ralf Baechle
2001-01-29  8:44             ` Geert Uytterhoeven
2001-01-29 21:54               ` Ralf Baechle
2001-01-29 15:57         ` Maciej W. Rozycki
2001-01-30  0:12           ` Mike McDonald
2001-01-30  9:46             ` Maciej W. Rozycki
2001-01-28 18:27     ` Geert Uytterhoeven
2001-01-26 20:28 ` Jun Sun

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=200101272257.OAA05689@saturn.mikemac.com \
    --to=mikemac@mikemac.com \
    --cc=K.H.C.vanHouten@research.kpn.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