All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Mike McDonald <mikemac@mikemac.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross compiling RPMs
Date: Fri, 26 Jan 2001 12:28:38 -0800	[thread overview]
Message-ID: <20010126122838.F9325@mvista.com> (raw)
In-Reply-To: <200101261815.KAA08917@saturn.mikemac.com>; from mikemac@mikemac.com on Fri, Jan 26, 2001 at 10:15:21AM -0800

On Fri, Jan 26, 2001 at 10:15:21AM -0800, Mike McDonald wrote:
> 
>   Can anyone point me to some references of techniques for cross
> compiling RPMs? I want to build some packages for my little endian
> MIPS but I haven't found any info on cross compiling RPMs in the RPM
> docs nor "Maximum RPM". Any pointers would be appreciated. (I'm
> particularly interested in how to specify the tool chain.)
>

Mike,

Most GNU packages allow you to specify environment variables such
as CC, AR, RANLIB, etc when invoking the "configure" command.  So
you will need to set those variables in your spec file
where "configure" is invoked.

If a package itself is not cross-compiling friendly, you need to 
make it cross-compilable first. :-)

If you only cross-compile one package, I suggest you read through
spec file and do the job manually (untar, applying patch, configure,
make, make install, etc).

Jun

      parent reply	other threads:[~2001-01-26 20:29 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
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 [this message]

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=20010126122838.F9325@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mikemac@mikemac.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.