public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: stefan@binarchy.net
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] cross compiling for a slow system
Date: Sat, 14 Aug 2004 19:03:06 +0200	[thread overview]
Message-ID: <20040814170306.GA18696@dice.seeling33.de> (raw)


I have a laptop with a p2 running at 300mhz and 128mb ram.
While this is enough for ssh sesions to other hosts at work 
and browsing the web, or even playing a film with mplayer,  
everytime glibc gets updated I start looking out for alternatives 
to building glibc on the laptop. It simply takes too much time.

I run distcc to compile most packages on the laptop, and
together with the 3 other gentoo hosts on my lan compilation
times for most packages are acceptable. But glibc does not
build with distcc.

Is there an easy automated way to build huge packages such as 
glibc, xorg and mozilla as a tbz package on a fast system, using 
foreign C- and USEFLAGS, and then install the tbz's on the target host?

And if not, how easily do you reckon this could be implemented in
portage? I'm quite profficient in python, so I might give this a go 
in my free time if it did not require a near portage rewrite.

thanks
stefan

-- 
Imagine a science-fiction device that allows any sort of food or 
physical object to be infinitely duplicated. If somebody then tried 
to sell you a tire for your car, why in the world would you buy it? 
- from "Open Source Development with CVS" (Fogel, Bar)

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2004-08-14 17:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 17:03 stefan [this message]
2004-08-14 17:12 ` [gentoo-dev] cross compiling for a slow system Ciaran McCreesh
2004-08-15 19:29 ` Ned Ludd

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=20040814170306.GA18696@dice.seeling33.de \
    --to=stefan@binarchy.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /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