1 |
On 14/05/17 15:56, Stuart Longland wrote: |
2 |
> On 14/05/17 14:23, Joshua Kinard wrote: |
3 |
>> On 05/13/2017 23:54, Stuart Longland wrote: |
4 |
>>> Hi all, |
5 |
>>> |
6 |
>>> I've decided to dust off the old Lemote Yeeloong that I have kicking |
7 |
>>> around for use as a throw-around netbook for on-the-road use. |
8 |
>>> |
9 |
>>> The aim is to have a machine that can do some basic web browsing (using |
10 |
>>> a decent browser, dillo won't cut it), image editing, and maybe some |
11 |
>>> amateur radio stuff (yes, done PSK31 with this beast before, operating |
12 |
>>> as VK4MM, so it does work). |
13 |
|
14 |
Well, a progress update… I have stage 1 and 2 tarballs built. Yes, |
15 |
that's after nearly a fortnight of compiling… with me putting the build |
16 |
host into hibernate mode since the machine emulates a vacuum cleaner in |
17 |
more ways than one! |
18 |
|
19 |
It has just started the stage 3, then coughed up the following: |
20 |
> Total: 30 packages (28 new, 2 reinstalls), Size of downloads: 8974 KiB |
21 |
> |
22 |
> * Error: circular dependencies: |
23 |
> |
24 |
> (sys-libs/libcap-2.25:0/0::gentoo, ebuild scheduled for merge) depends on |
25 |
> (virtual/pam-0-r1:0/0::gentoo, ebuild scheduled for merge) (buildtime) |
26 |
> (sys-libs/pam-1.3.0:0/0::gentoo, ebuild scheduled for merge) (runtime) |
27 |
> (sys-libs/libcap-2.25:0/0::gentoo, ebuild scheduled for merge) (buildtime) |
28 |
> |
29 |
> It might be possible to break this cycle |
30 |
> by applying the following change: |
31 |
> - sys-libs/pam-1.3.0 (Change USE: -filecaps) |
32 |
> |
33 |
> Note that this change can be reverted, once the package has been installed. |
34 |
> |
35 |
> !!! catalyst: run script failed. |
36 |
> |
37 |
> |
38 |
> Traceback (most recent call last): |
39 |
> File "modules/generic_stage_target.py", line 1244, in run_local |
40 |
> "run script failed.",env=self.env) |
41 |
> File "/usr/lib64/catalyst/modules/catalyst_support.py", line 541, in cmd |
42 |
> raise CatalystError,myexc |
43 |
> CatalystError |
44 |
> None |
45 |
> |
46 |
> !!! catalyst: Stage build aborting due to error. |
47 |
|
48 |
Not sure if anyone else doing stage builds has struck that (haven't seen |
49 |
it on x86 and AMD64). I've just re-started Catalyst, hit ^Z at the |
50 |
appropriate point and chrooted in myself to temporarily merge |
51 |
sys-libs/pam (with USE=-filecaps as suggested) to see if I can work it |
52 |
past that first blocker. |
53 |
|
54 |
(You'd think portage would be smart enough to figure this out itself? |
55 |
Ahh well.) |
56 |
|
57 |
Seems strange though… maybe something is up with the n64 profiles, or |
58 |
maybe something got missed at stage 2. If that's all that goes wrong |
59 |
though, I should have shiny new experimental n64 little-endian stages |
60 |
for people in a week or so. |
61 |
|
62 |
I might also see what's up with SMP support on this VM so I can throw a |
63 |
bit more CPU muscle at the problem. Seems a waste to have 5 host CPU |
64 |
cores doing practically nothing and one getting flogged by a VM when the |
65 |
same host will churn out x86 and AMD64 stages within a day. |
66 |
-- |
67 |
Stuart Longland (aka Redhatter, VK4MSL) |
68 |
|
69 |
I haven't lost my mind... |
70 |
...it's backed up on a tape somewhere. |