From: "J García" <jyo.garcia@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] gcc-6.4.0-r1::gentoo failed (compile phase)
Date: Thu, 29 Mar 2018 07:33:11 -0600 [thread overview]
Message-ID: <CAGQH77f8faBke+xZemnht_ER6GOUTTzqZEz=_m_hYHgO7JKBCg@mail.gmail.com> (raw)
In-Reply-To: <899d5b2b-c748-b9aa-7df0-327d8834e8cd@sys-concept.com>
2018-03-28 12:08 GMT-06:00 <thelma@sys-concept.com>:
> I'm still searching for a good guid howto over NFS.
> It is till not clear to me what to do before or after. I need to start
> with emerging NFS :-/
>
> On my Atom-330 with MAKEOPTS="-j1" it took me over 12-hours to compile
> just gcc-6.4.0-r1 :-/
> and I have server on that network 8-core AMD with 32-GB or RAM (so I
> might as well put it into a good use).
I would not bother with NFS for this, portage has some options you can
add to make.conf to transfer the binary packages using HTTP, namely
FEATURES=getbinpkg and the variable PORTAGE_BINHOST, you can add those
to the less powerful machine, check the manual about make.conf for the
details on each.
An example:
PORTAGE_BINHOST="http://10.0.0.X:8000"
Just make it appropriate for your LAN, then run a simple HTTP server
on the directory that contains the binary packages on the powerful
machine, no need install any HTTP server package, python can do it
[1][2]:
For example:
$ cd $PKGDIR
$ python2 -m SimpleHTTPServer 8000
or
$ python3 -m http.server 8000
You can even add that as part of the service that creates the chroot
as suggested before.
.
[1] https://docs.python.org/3.6/library/http.server.html?highlight=httpserver#module-http.server
[2] https://docs.python.org/2/library/simplehttpserver.html#module-SimpleHTTPServer
next prev parent reply other threads:[~2018-03-29 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 11:30 [gentoo-user] gcc-6.4.0-r1::gentoo failed (compile phase) thelma
2018-03-27 9:19 ` Helmut Jarausch
2018-03-27 15:25 ` [gentoo-user] [SOLVED] " thelma
2018-03-28 7:32 ` Peter Humphrey
2018-03-28 15:14 ` thelma
2018-03-28 16:40 ` Peter Humphrey
2018-03-28 18:08 ` thelma
2018-03-28 20:54 ` thelma
2018-03-29 13:33 ` J García [this message]
2018-03-28 20:51 ` [gentoo-user] " Ian Zimmerman
2018-03-28 21:08 ` Grant Taylor
2018-03-28 21:53 ` Ian Zimmerman
2018-03-28 22:09 ` Grant Taylor
2018-03-28 22:43 ` Ian Zimmerman
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='CAGQH77f8faBke+xZemnht_ER6GOUTTzqZEz=_m_hYHgO7JKBCg@mail.gmail.com' \
--to=jyo.garcia@gmail.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