1 |
On 4/2/19 5:17 PM, Daniel Frey wrote: |
2 |
> Well, I haven't been bitten for quite a while now (years)... |
3 |
> |
4 |
> I have been doing updates to my mythtv frontends and I noticed this time |
5 |
> around updating has been taking FOREVER. Something in this round of |
6 |
> updates broke distcc (which worked the last update run.) In addition, I |
7 |
> have multiple packages failing the same way: |
8 |
> |
9 |
> distcc[3596] (dcc_open_lockfile) ERROR: failed to creat |
10 |
> /var/tmp/portage/dev-libs/glib-2.58.3/homedir/.distcc/lock/cpu_localhost_0: |
11 |
> Permission denied |
12 |
> distcc[3596] (dcc_lock_one) ERROR: failed to lock |
13 |
> distcc[3596] (dcc_open_state) ERROR: failed to open |
14 |
> /var/tmp/portage/dev-libs/glib-2.58.3/homedir/.distcc/state/binstate_3596: |
15 |
> Permission denied |
16 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
17 |
> .libs/libglib_2_0_la-gprintf.o: warning: relocation against |
18 |
> `stdout@@GLIBC_2.2.5' in read-only section `.text' |
19 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
20 |
> .libs/libglib_2_0_la-gmessages.o: relocation R_X86_64_PC32 against |
21 |
> symbol `stderr@@GLIBC_2.2.5' can not be used when making a shared |
22 |
> object; recompile with -fPIC |
23 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: |
24 |
> final link failed: Bad value |
25 |
> collect2: error: ld returned 1 exit status |
26 |
> |
27 |
> |
28 |
> This example is glib, but lirc failed the same way. |
29 |
> |
30 |
> I don't know if the nonfunctioning distcc is causing these problem and |
31 |
> searching for locking errors yields results from 2003 or so. |
32 |
> |
33 |
> Anyone seen this? So far distcc has failed on all machines, and two |
34 |
> machines have errors almost identical to the above. |
35 |
> |
36 |
> Dan |
37 |
> |
38 |
|
39 |
I've decided to try an emerge -e @system... don't know if that will fix |
40 |
anything. |
41 |
|
42 |
Dan |