From: Pete Popov <ppopov@mvista.com>
To: Mike McDonald <mikemac@mikemac.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross compiling RPMs
Date: Fri, 26 Jan 2001 11:39:17 -0800 [thread overview]
Message-ID: <3A71D265.231904BB@mvista.com> (raw)
In-Reply-To: 200101261927.LAA09872@saturn.mikemac.com
Mike McDonald wrote:
>
> >Date: Fri, 26 Jan 2001 10:37:03 -0800
> >From: Pete Popov <ppopov@mvista.com>
> >To: Mike McDonald <mikemac@mikemac.com>
> >Subject: Re: Cross compiling RPMs
>
> >To start with, you'll need a cross tool chain setup properly with the
> >headers and libraries. One option is
> >ftp.mvista.com:/pub/Area51/mips_fp_le. You can grab everything (the
> >entire root fs) or just the tools: binutils, gcc, kernel headers,
> >glibc. Others might have similar toolchains they can point you at.
> >Another option is native builds, which I personally don't like.
> >
> >Pete
>
> I have a working tool chain that I use to cross compile a kernel
> with sources from. How do I convince rpm to use that chain?
Is that tool chain setup to compile userland apps? Can you cross compile
this:
hello.c:
int main()
{
printf("hello world\n");
}
with a command such as "mips_fp_le-gcc -o hello hello.c" and get a
little endian mips binary that runs on your system?
If so, then you need to modify the .spec file for the given rpm to pick
up the right tool chain, ... and you'll probably need to add macro files
that rpm picks up so that you can do something like:
rpm -ba --target=xxxxx <spec file>
it works.
That's easier said than done. I wouldn't know how to do it myself --
someone else has done it for me here.
Pete
next prev parent reply other threads:[~2001-01-26 19:39 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 [this message]
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
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=3A71D265.231904BB@mvista.com \
--to=ppopov@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.