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
It took me forever to sort out why I was getting "dpkg-shlibdeps: warning: cannot find library" for an internal library in my package, even as I was using the -l parameter to point to it.
I eventually realized that by calling dpkg-shlibdeps -l directly it would work fine. dh_shlibdeps wasn't passing along the -l as specified. The workaround was to use -- and then pass -l directly to dpkg-shlibdeps unchanged.
Looking into the code, dh_shlibdeps will prepend a slash to make the path absolute. I also found that this used to be documented, but it's been dropped from the man page.
This came up when I was using pdebuild, so maybe it's something related to the chroot? I really don't know the reason for the absolute forcing in the first place; it seems to work fine without.
Anyway, I'd at least restore the mention of relative paths being made absolute in the man page, or reevaluate the forcing altogether.
Sadly, I do not have a quick answer to the problem you are facing. I have refiled it as https://bugs.debian.org/1042483 as a reminder to follow up later.
It took me forever to sort out why I was getting "dpkg-shlibdeps: warning: cannot find library" for an internal library in my package, even as I was using the -l parameter to point to it.
I eventually realized that by calling dpkg-shlibdeps -l directly it would work fine. dh_shlibdeps wasn't passing along the -l as specified. The workaround was to use -- and then pass -l directly to dpkg-shlibdeps unchanged.
Looking into the code, dh_shlibdeps will prepend a slash to make the path absolute. I also found that this used to be documented, but it's been dropped from the man page.
This came up when I was using pdebuild, so maybe it's something related to the chroot? I really don't know the reason for the absolute forcing in the first place; it seems to work fine without.
Anyway, I'd at least restore the mention of relative paths being made absolute in the man page, or reevaluate the forcing altogether.
debhelper/dh_shlibdeps
Line 192 in 5d1bb29
The text was updated successfully, but these errors were encountered: