| 1 |
On Tuesday, 11 May 2021 15:47:40 BST Peter Humphrey wrote: |
| 2 |
> Hello list, |
| 3 |
> |
| 4 |
> I'm having problems with libreoffice. I thought at first it was a space |
| 5 |
> problem, after the recent thread on running out of it, but I now have /tmp |
| 6 |
> as part of /, not separate, and /var/tmp/portage on a 100GB partition of a |
| 7 |
> SATA SSD. The root partition has 35GB spare. |
| 8 |
> |
| 9 |
> Before I try again with /tmp on its own partition, does the following |
| 10 |
> extract from the emerge log file ring any bells? |
| 11 |
|
| 12 |
There's no benefit in having the whole /tmp on disk, just /var/tmp/portage |
| 13 |
will do. Also you can leave /var/tmp/portage on RAM and just mount-bind it |
| 14 |
when big packages are expected to exhaust available RAM; e.g. something like |
| 15 |
this would work: |
| 16 |
|
| 17 |
mkdir /var_tmp_portage |
| 18 |
chown -v portage:portage /var_tmp_portage |
| 19 |
mount -o bind /var/tmp/portage /var_tmp_portage |
| 20 |
|
| 21 |
You would probably need '-o exec' too. 35G on / fs is more than enough for |
| 22 |
LO. |
| 23 |
|
| 24 |
|
| 25 |
> --->8 |
| 26 |
> [CAT] CustomTarget/sysui/share/libreofficedev/create_tree.sh |
| 27 |
> mkdir -p /mnt/scratch/tmp/portage/app-office/libreoffice-6.4.7.2/work/ |
| 28 |
> libreoffice-6.4.7.2/ |
| 29 |
> workdir/CustomTarget/sysui/share/libreofficedev/ |
| 30 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/ |
| 31 |
> ld: /usr/lib/g |
| 32 |
> cc/x86_64-pc-linux-gnu/10.3.0/../../../../lib64/libpoppler.so: undefined |
| 33 |
> reference to `std |
| 34 |
> |
| 35 |
> ::__throw_bad_array_new_length()@GLIBCXX_3.4.29' |
| 36 |
|
| 37 |
I don't know why poppler complains, unless someone more knowledgeable chimes |
| 38 |
in, it may be worth rebuilding glibc, poppler and trying again. |
Archives