public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: crossdev setup questions for distcc usage
Date: Fri, 20 Mar 2015 14:02:19 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150320T143833-309@post.gmane.org> (raw)
In-Reply-To: 20150319213108.GA11283@waltdnes.org

Walter Dnes <waltdnes <at> waltdnes.org> writes:



> PORTDIR_OVERLAY="/usr/local/portage ${PORTDIR_OVERLAY}"


PORTDIR is deprecated, from my understanding as to the new
schemes for repos and the namespaces[1]. We're in a transition,
so this might be an excellent issue to flush out  with the devs[2].


As soon as you (cross)compile with more than one
core, things that work and do not work seem to often be ambiguous
on the results. From what I've experienced over the years and read,
it may be best to keep the flag setting extremely conservative
and test your results before using more aggressively experimental
configurations. I have not done much of this since I built some
i586 (amd&intel) binaries for minimized gentoo systems quite a few
years ago.


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 have several old 586 and 686 based systems laying around,
so I can duplicate and verify your results if you like. Also, lots 
of linux distros compile for target 386 binaries so they run everywhere; it
might be a good resources if you can find where one of those niche linux
distros describe how they cross compile for their periodic releases.

ZeroChaos (gentoo dev) releases i686 codes for pentoo, so that might be
another source of expertise you can use as a guide.[3]


hth,
James


[1] {gentoo-dev} Naming of repositories (3/14/15)

[2] https://wiki.gentoo.org/wiki/Project:Portage/Sync

[3] http://www.pentoo.ch/download/tools_list_i686_2014_0_RC3_5





  parent reply	other threads:[~2015-03-20 14:02 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 ` James [this message]
2015-03-21 10:13   ` [gentoo-user] " Walter Dnes

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=loom.20150320T143833-309@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --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