Bug 704066 – gnome-base/gvfs-1.40.2 : /.../ld: cannot find -lpsx

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Toralf Förster 2019-12-28 08:58:28 UTC]

x86_64-pc-linux-gnu-gcc  -o daemon/gvfsd-admin 'daemon/f77b12a@@gvfsd-admin@exe/daemon-main.c.o' 'daemon/f77b12a@@gvfsd-admin@exe/daemon-main-generic.c.o' 'daemon/f77b12a@@gvfsd-admin@exe/gvfsbackendadmin.c.o' -Wl,--as-needed -Wl,--no-undefined -O2 -pipe -march=native -Wl,-O1 -Wl,--as-needed -Wl,--start-group daemon/libgvfsdaemon.so common/libgvfscommon.so /usr/lib64/libgio-2.0.so /usr/lib64/libgobject-2.0.so /usr/lib64/libglib-2.0.so /usr/lib64/libcap.so -lpthread -Wl,-wrap,pthread_create -lpsx /usr/lib64/libpolkit-gobject-1.so -Wl,--end-group '-Wl,-rpath,$ORIGIN/:$ORIGIN/../common' -Wl,-rpath-link,/var/tmp/portage/gnome-base/gvfs-1.40.2/work/gvfs-1.40.2-build/daemon -Wl,-rpath-link,/var/tmp/portage/gnome-base/gvfs-1.40.2/work/gvfs-1.40.2-build/common
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lpsx
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
 * ERROR: gnome-base/gvfs-1.40.2::gentoo failed (compile phase):

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_desktop_gnome-libressl-20191225-141513

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-9.2.0 *

clang:
clang version 9.0.1 
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/9/bin
llvm:
9.0.1
Available Python interpreters, in order of preference:
  [1]   python3.7
  [2]   python3.6
  [3]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems)
  [2]   ruby25 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.40.0 *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.13.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

repository:
==> /var/db/repos/gentoo/metadata/timestamp.chk <==
Sat, 28 Dec 2019 04:05:32 +0000

emerge -qpvO gnome-base/gvfs
[ebuild  N    ] gnome-base/gvfs-1.40.2  USE="cdda elogind gnome-keyring gnome-online-accounts http policykit udev udisks -afp -archive -bluray -fuse -google -gphoto2 -ios -mtp -nfs -samba -systemd -test -zeroconf"

[Comment 1 Toralf Förster 2019-12-28 08:58:31 UTC]

Created attachment 601498 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2019-12-28 08:58:35 UTC]

Created attachment 601500 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2019-12-28 08:58:39 UTC]

Created attachment 601502 [details]
environment

[Comment 4 Toralf Förster 2019-12-28 08:58:42 UTC]

Created attachment 601504 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2019-12-28 08:58:45 UTC]

Created attachment 601506 [details]
gnome-base:gvfs-1.40.2:20191228-041908.log

[Comment 6 Toralf Förster 2019-12-28 08:58:48 UTC]

Created attachment 601508 [details]
logs.tbz2

[Comment 7 Toralf Förster 2019-12-28 08:58:51 UTC]

Created attachment 601510 [details]
temp.tbz2

[Comment 8 George Diamantopoulos 2019-12-28 15:32:27 UTC]

I'm also getting this on a new installation, but with systemd failing instead. Any known workarounds?

[Comment 9 Toralf Förster 2019-12-28 15:35:38 UTC]

(In reply to George Diamantopoulos from comment #8)
> I'm also getting this on a new installation, but with systemd failing
> instead. Any known workarounds?

emerge libcap-2.29-r1 (do you have 2.29, right?)

[Comment 10 George Diamantopoulos 2019-12-28 15:43:14 UTC]

Just figured that out, I downgraded to 2.28 instead, as I hadn't synced recently... Thanks!

[Comment 11 Mart Raudsepp 2019-12-29 22:19:24 UTC]

So I assume this is a fallout from sys-libs/libcap-2.29 temporary problem (bug 703912 and others), and not a problem anymore.