| 1 |
On Sunday, 6 May 2018 11:18:40 BST Wols Lists wrote: |
| 2 |
> On 03/05/18 16:22, Peter Humphrey wrote: |
| 3 |
> > On Thursday, 3 May 2018 15:58:44 BST Mick wrote: |
| 4 |
> >> Is there anything I can do with the existing laptop and its limited |
| 5 |
> >> resources to speed up chromium's emerge? |
| 6 |
> > |
| 7 |
> > All I can suggest is to build a package in a chroot on a speedier machine |
| 8 |
> > and transfer it to the laptop. That's how I cope with a very slow 32-bit |
| 9 |
> > single- core Atom box. |
| 10 |
> |
| 11 |
> Is distcc still there? I set that up ages ago, and when it was working |
| 12 |
> it worked great. Trouble is, I think it got messed up in an emerge and I |
| 13 |
> never set it up again. |
| 14 |
> |
| 15 |
> Cheers, |
| 16 |
> Wol |
| 17 |
|
| 18 |
Yes, it's still there - see below - although I've never used it. For really |
| 19 |
slow PCs I emerge everything within a chroot on a fast PC and then rsync all |
| 20 |
binpkg over to the slow PC and emerge them locally. |
| 21 |
|
| 22 |
eix -l distcc |
| 23 |
* sec-policy/selinux-distcc |
| 24 |
Available versions: |
| 25 |
~ 2.20170204-r1 |
| 26 |
2.20170204-r2 |
| 27 |
2.20170204-r3 |
| 28 |
2.20170204-r4 |
| 29 |
2.20170805-r2 |
| 30 |
2.20170805-r3 |
| 31 |
~ 2.20170805-r4 |
| 32 |
2.20180114-r1 |
| 33 |
~ 2.20180114-r2 |
| 34 |
** 9999 |
| 35 |
Homepage: https://wiki.gentoo.org/wiki/Project:SELinux |
| 36 |
Description: SELinux policy for distcc |
| 37 |
|
| 38 |
* sys-devel/distcc |
| 39 |
Available versions: |
| 40 |
3.1-r10 ^t [avahi gtk hardened ipv6 selinux xinetd |
| 41 |
PYTHON_TARGETS="python2_7"] ["python_targets_python2_7"] |
| 42 |
3.2_rc1-r4 ^t [crossdev gnome gssapi gtk hardened ipv6 selinux |
| 43 |
xinetd zeroconf PYTHON_TARGETS="python2_7"] ["python_targets_python2_7"] |
| 44 |
~ 3.2_rc1-r5 ^t [gnome gssapi gtk hardened ipv6 selinux xinetd |
| 45 |
zeroconf PYTHON_TARGETS="python2_7"] ["python_targets_python2_7"] |
| 46 |
[M]~ 3.3 ^t [gnome gssapi gtk hardened ipv6 selinux xinetd |
| 47 |
zeroconf PYTHON_SINGLE_TARGET="python3_5 python3_6" PYTHON_TARGETS="python3_5 |
| 48 |
python3_6"] ["^^ ( python_single_target_python3_5 |
| 49 |
python_single_target_python3_6 ) python_single_target_python3_5? ( |
| 50 |
python_targets_python3_5 ) python_single_target_python3_6? ( |
| 51 |
python_targets_python3_6 )"] Michał Górny <mgorny@g.o> (20 Mar 2018) |
| 52 |
Poorly tested version bump followed by a series of quick hacks that do not |
| 53 |
make it any more working. Bug #651030. |
| 54 |
Homepage: http://distcc.org/ |
| 55 |
Description: Distribute compilation of C code across several |
| 56 |
machines on a network |
| 57 |
|
| 58 |
Found 2 matches |
| 59 |
|
| 60 |
-- |
| 61 |
Regards, |
| 62 |
Mick |
Archives