Ubuntu
smc-tools package

  1. Bug #2009495
  2. Comment #7

Comment 7 for bug 2009495

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2023-03-15 13:41 EDT-------
(In reply to comment #7)
> Hello Halil, so this is caused by a missing (build) dependency of a tool
> that is used in the Makefile (lsb_release).
> If it's in place 'libsmc-preload.so' will be installed on Ubuntu at
> '/usr/lib/s390-linux-gnu/libsmc-preload.so' - according to the upstream
> Makefile code (so not in /usr/lib).
> Should it be in /usr/lib instead or at least sym-linked to /usr/lib?
> If not, it's okay with the fixed build dependency, if not I need to tweak
> the packaging (or even the Makefile).

Hello Frank!

Sorry I have no direct answer for your question. My understanding of this multiarch stuff is not sufficient.

In what cases are shared libraries meant to be in /usr/lib or symlinked to it? I had a quick stab at the corresponding documentation, but I failed to figure it out. Do libraries that have the same architecture as the dpkg --print-architecture reports have to go under /usr/lib/<triplet> or rather under /usr/lib (in which case only the foreign architecture shared libraries would go under /usr/lib/<triplet>). Based on the specs I have read I lean towards the former, but I'm far from confident, and your question makes me ask myself if it is actually the latter.