public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: stefan@binarchy.net
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] cross compiling for a slow system
Date: 15 Aug 2004 15:29:57 -0400	[thread overview]
Message-ID: <1092598196.4708.67.camel@simple> (raw)
In-Reply-To: <20040814170306.GA18696@dice.seeling33.de>

[-- Attachment #1: Type: text/plain, Size: 2290 bytes --]

cross compiling usually means your host and target arches are not the
same. I'm guessing this is not the case so chances are your not really
cross compiling.

If you are really cross compiling then the following packages in a base
system are going to give you problems as they are not really cross aware
_yet_

app-shells/bash-3.0-r4
app-shells/sash-3.7
dev-lang/perl-5.8.4-r1
dev-lang/python-2.3.4
net-misc/iputils-021109-r3
net-misc/rsync-2.6.0-r2
sys-apps/coreutils-5.2.1-r1
sys-apps/file-4.10
sys-apps/kbd-1.12-r2
sys-apps/less-382-r2
sys-apps/procps-3.2.2-r1
sys-apps/psmisc-21.4
sys-apps/shadow-4.0.4.1-r3
sys-apps/texinfo-4.7-r1
sys-devel/libtool-1.5.2-r5
sys-fs/e2fsprogs-1.35
sys-libs/cracklib-2.7-r9
sys-libs/ncurses-5.4-r3
sys-apps/module-init-tools-3.0-r2
net-misc/openssh-3.8.1_p1-r1

Assuming your both of your systems are x86 based then this is really a
trivial task.

First try to match your USE= as close as you can then emerge -B from
your build host and then just scp the package into your target host
/usr/portage/packages/All/ then emerge -(k|K) on your target host to
install it.

On Sat, 2004-08-14 at 13:03, stefan@binarchy.net wrote:
> 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
-- 
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-08-15 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 17:03 [gentoo-dev] cross compiling for a slow system stefan
2004-08-14 17:12 ` Ciaran McCreesh
2004-08-15 19:29 ` Ned Ludd [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=1092598196.4708.67.camel@simple \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=stefan@binarchy.net \
    /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