Bug 600592

Summary:	net-fs/samba-4.2.14 with FEATURES=distcc installs broken libsmbclient.so
Product:	Gentoo Linux	Reporter:	Victor Mataré <vmatare+gbug>
Component:	Current packages	Assignee:	Gentoo's SAMBA Team <samba>
Status:	UNCONFIRMED ---
Severity:	normal	CC:	crabbedhaloablution, jstein, walther
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=581900
Whiteboard:
Package list:		Runtime testing required:	---

Description Victor Mataré 2016-11-23 15:25:33 UTC

I have two ~amd64 systems, but strangely, only one has this issue. The problem is that all of the libsmbclient.so dependencies live in /usr/lib/samba and are supposed to be found via the DT_RUNPATH dynamic section attribute in libsmbclient.so.

So on the working machine I see:

# objdump -p /usr/lib/libsmbclient.so | grep RUNPATH
  RUNPATH              /usr/lib64/samba:/usr/lib64

Whereas on the broken machine I get:

# objdump -p /usr/lib/libsmbclient.so | grep RUNPATH
  RUNPATH              /usr/lib64

Which of course yields build failures for anything linking against libsmbclient.so. Both machines differ mainly in their USE flags, so I'll continue to investigate what triggers the problem, but of course something like this should not happen at all, no matter the USE flags.

Comment 1 Victor Mataré 2016-12-10 15:31:37 UTC

Okay, this seems to be triggered by FEATURES=distcc. Once I disable distcc, the correct RUNPATH is put into the library. Not sure how to proceed with this. On the one hand, there's a bunch of packages that fail to build with distcc, so maybe we don't care all that much, but those are normally pretty obvious build errors. Whereas in this case, we end up with lots of secondary problems that may be pretty hard to track down for many users.

Comment 2 Ben Kohler gentoo-dev

2022-07-28 19:24:42 UTC

*** Bug 617556 has been marked as a duplicate of this bug. ***