[gentoo-user] Compiling/loading problem

[gentoo-user] Compiling/loading problem

[Peter Humphrey]

Hello list,

I'm having problems with libreoffice. I thought at first it was a space problem, 
after the recent thread on running out of it, but I now have /tmp as part of 
/, not separate, and /var/tmp/portage on a 100GB partition of a SATA SSD. The 
root partition has 35GB spare.

Before I try again with /tmp on its own partition, does the following extract 
from the emerge log file ring any bells?

--->8
[CAT] CustomTarget/sysui/share/libreofficedev/create_tree.sh
mkdir -p /mnt/scratch/tmp/portage/app-office/libreoffice-6.4.7.2/work/
libreoffice-6.4.7.2/
workdir/CustomTarget/sysui/share/libreofficedev/
/usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/
ld: /usr/lib/g
cc/x86_64-pc-linux-gnu/10.3.0/../../../../lib64/libpoppler.so: undefined 
reference to `std
::__throw_bad_array_new_length()@GLIBCXX_3.4.29'
echo "#!/bin/sh" > /mnt/scratch/tmp/portage/app-office/libreoffice-6.4.7.2/work/
libreoffic
e-6.4.7.2/workdir/CustomTarget/sysui/share/libreoffice/create_tree.sh
collect2: error: ld returned 1 exit status
--->8

There's also qtwebengine to get through when I have this one fixed.

-- 
Regards,
Peter.

Re: [gentoo-user] Compiling/loading problem

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]

On Tuesday, 11 May 2021 15:47:40 BST Peter Humphrey wrote:
> Hello list,
> 
> I'm having problems with libreoffice. I thought at first it was a space
> problem, after the recent thread on running out of it, but I now have /tmp
> as part of /, not separate, and /var/tmp/portage on a 100GB partition of a
> SATA SSD. The root partition has 35GB spare.
> 
> Before I try again with /tmp on its own partition, does the following
> extract from the emerge log file ring any bells?

There's no benefit in having the whole /tmp on disk, just /var/tmp/portage 
will do.  Also you can leave /var/tmp/portage on RAM and just mount-bind it 
when big packages are expected to exhaust available RAM; e.g. something like 
this would work:

mkdir /var_tmp_portage
chown -v portage:portage /var_tmp_portage
mount -o bind /var/tmp/portage /var_tmp_portage

You would probably need '-o exec' too.  35G on / fs is more than enough for 
LO.


> --->8
> [CAT] CustomTarget/sysui/share/libreofficedev/create_tree.sh
> mkdir -p /mnt/scratch/tmp/portage/app-office/libreoffice-6.4.7.2/work/
> libreoffice-6.4.7.2/
> workdir/CustomTarget/sysui/share/libreofficedev/
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.3.0/../../../../x86_64-pc-linux-gnu/bin/
> ld: /usr/lib/g
> cc/x86_64-pc-linux-gnu/10.3.0/../../../../lib64/libpoppler.so: undefined
> reference to `std
> 
> ::__throw_bad_array_new_length()@GLIBCXX_3.4.29'

I don't know why poppler complains, unless someone more knowledgeable chimes 
in, it may be worth rebuilding glibc, poppler and trying again.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Compiling/loading problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

On Tue, 11 May 2021 16:08:13 +0100, Michael wrote:

> > Before I try again with /tmp on its own partition, does the following
> > extract from the emerge log file ring any bells?  
> 
> There's no benefit in having the whole /tmp on disk, just
> /var/tmp/portage will do.  Also you can leave /var/tmp/portage on RAM
> and just mount-bind it when big packages are expected to exhaust
> available RAM; e.g. something like this would work:
> 
> mkdir /var_tmp_portage
> chown -v portage:portage /var_tmp_portage
> mount -o bind /var/tmp/portage /var_tmp_portage

Or just

PORTAGE_TMPDIR="/lots/of/space" emerge -1a bigpackage


-- 
Neil Bothwick

Of course it's not your day,
With 7 billion people on earth chances are slim it will ever be *your*
day.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]