You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Samba4 by default uses two rpaths, one public (/usr/lib) and a private (/usr/lib/samba), so all bins have those set to: /usr/lib/samba:/usr/lib
The default RSTRIP macro will break those paths via rstrip.sh to: /usr/lib/samba XXXXXXXX
This results in broken bin's and my temp fix is this: RSTRIP:=:
Just wanted to ask if this is a bug we want to fix, by allowing multiple rpaths in bins, if they are defined or keep as samba4 specific build quirk?
PS: The main use-case is to avoid/circumvent build issues and let samba use some of its own bundled system lib versions, like tevent or tdb, com_err and than make those private to avoid breaking other packages.
The text was updated successfully, but these errors were encountered:
The rstrip.sh script is supposed to retain paths starting with /lib or /usr/lib so I'm not sure whats wrong there. Maybe try adding some debug echos to rstrip.sh
Maintainer: @jow- @neheb
Environment: all
Description:
Samba4 by default uses two rpaths, one public (/usr/lib) and a private (/usr/lib/samba), so all bins have those set to:
/usr/lib/samba:/usr/lib
The default RSTRIP macro will break those paths via rstrip.sh to:
/usr/lib/samba XXXXXXXX
This results in broken bin's and my temp fix is this:
RSTRIP:=:
Just wanted to ask if this is a bug we want to fix, by allowing multiple rpaths in bins, if they are defined or keep as samba4 specific build quirk?
PS: The main use-case is to avoid/circumvent build issues and let samba use some of its own bundled system lib versions, like tevent or tdb, com_err and than make those private to avoid breaking other packages.
The text was updated successfully, but these errors were encountered: