public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: crossdev setup questions for distcc usage
Date: Sat, 21 Mar 2015 06:13:33 -0400	[thread overview]
Message-ID: <20150321101333.GA23185@waltdnes.org> (raw)
In-Reply-To: <loom.20150320T143833-309@post.gmane.org>

On Fri, Mar 20, 2015 at 02:02:19PM +0000, James wrote

> I'm interested in exactly what you are doing, plus extending the
> cross compile to arm architectures and running on top of clusters
> of gentoo systems; please continue to post back what you discover.
> For this sort of (cluster compiling) experimentation, folks build
> custom 'frameworks' so you might have some luck adding 'framework'
> to your keyword searches related to distributed compiling.

  I'm simply trying to offload compiling from my ancient, underpowered
netbook (14 hours to build seamonkey!!!) to my desktop.  I'd like to be
able to transparently run "emerge" from the netbook, have the desktop
machine do the grunt work, and install the compiled binaries and
associated /etc/* files on the netbook.  This assumes both machines are
connected on my home LAN.

  Since you mentioned arm architectures, it's ironic that the wiki
crossdev instructions now point to the embedded cross-compiler site
http://www.gentoo.org/proj/en/base/embedded/handbook/

  I've followed the instructions chapter 2 for installing crossdev and
it appears to work.  Note that my desktop machine is a 64-bit install...

=======================================================================
[d531][root][~] i686-pc-linux-gnu-gcc --version
i686-pc-linux-gnu-gcc (Gentoo 4.9.2 p1.2, pie-0.6.2) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[d531][root][~] echo 'int main(){return 0;}' > ctest.c
[d531][root][~] i686-pc-linux-gnu-gcc -Wall ctest.c -o ctest
[d531][root][~] file ctest
ctest: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, not stripped
[d531][root][~]
=======================================================================

  I'm now reading up on...
https://wiki.gentoo.org/wiki/Distcc/Cross-Compiling
https://wiki.gentoo.org/wiki/Distcc

...to figure out how to launch it from my netbook.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


      reply	other threads:[~2015-03-21 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 21:31 [gentoo-user] crossdev setup questions for distcc usage Walter Dnes
2015-03-19 23:35 ` Walter Dnes
2015-03-20 14:02 ` [gentoo-user] " James
2015-03-21 10:13   ` Walter Dnes [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=20150321101333.GA23185@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@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