From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Florian Lohoff <flo@rfc822.org>, Pete Popov <ppopov@mvista.com>,
linux-mips@oss.sgi.com
Subject: Re: Cross compiling RPMs
Date: Sat, 27 Jan 2001 10:50:18 -0800 [thread overview]
Message-ID: <20010127105018.D867@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1010127083433.29150D-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Sat, Jan 27, 2001 at 08:42:34AM +0100
On Sat, Jan 27, 2001 at 08:42:34AM +0100, Maciej W. Rozycki wrote:
> > I definitly go for native builds - Once you have a working stable
> > base you can set up debian autobuilders which will do nearly
> > everything for you except signing and uploading the package into
> > the main repository.
>
> Yep, native builds are more likely to get correct as that's what most
> developers out there check (there are actually developers who never heard
> of something like a cross-compilation, sigh...). But not everyone can
> afford a week to build glibc or X11...
Sounds like DECstation results. Building all the Redhat 7.0 packages which
are on oss + some others which could build for MIPS but don't for some
reason to the point where the build fails takes approx 40h on an Origin 200
with 2 180MHz R10000 processors and 1.5gb RAM.
I recently was told there is some m68k VME system out there which needs
approx. 3 days to rebuild it's kernel.
Ralf
next prev parent reply other threads:[~2001-01-28 2:55 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 [this message]
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=20010127105018.D867@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ppopov@mvista.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