Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 648196 - ≤sys-libs/libchipcard-5.0.2 tries to find libpcsc* in /usr/lib instead of /usr/lib64
Summary: ≤sys-libs/libchipcard-5.0.2 tries to find libpcsc* in /usr/lib instead of /us...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Hanno Böck
URL:
Whiteboard:
Keywords:
Depends on: 658020
Blocks:
  Show dependency tree
 
Reported: 2018-02-19 21:36 UTC by Navid Zamani
Modified: 2018-07-14 15:00 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
SYMLINK_LIB_no.patch (SYMLINK_LIB_no.patch,720 bytes, patch)
2018-03-12 18:25 UTC, Navid Zamani
Details | Diff
libchipcard-5.0.2-r1.ebuild (libchipcard-5.0.2-r1.ebuild,1.12 KB, text/plain)
2018-03-12 18:29 UTC, Navid Zamani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Zamani 2018-02-19 21:36:32 UTC
The summary basically says it all.

Here’s the relevant emerge output:

…
checking if PC/SC should be used... yes
checking for pcsc includes... -I/usr/include -I/usr/include/PCSC
checking for pcsc libs... configure: WARNING: No pcsc libraries found, SCard driver will not be available.
configure: error: 
***** No pcsc libraries found.
***** Please install the pcsclite package including development packages.

I just checked, and pcsc-lite and -tools are installed, and the following files, owned by sys-apps/pcsc-lite-1.8.22, can be found:

/usr/lib64/libpcsclite.la
/usr/lib64/libpcsclite.so -> libpcsclite.so.1.0.0
/usr/lib64/libpcsclite.so.1 -> libpcsclite.so.1.0.0
/usr/lib64/libpcsclite.so.1.0.0
/usr/lib64/libpcscspy.la
/usr/lib64/libpcscspy.so -> libpcscspy.so.0.0.0
/usr/lib64/libpcscspy.so.0 -> libpcscspy.so.0.0.0
/usr/lib64/libpcscspy.so.0.0.0

On my system, /usr/lib is NOT a symlink to /usr/lib32 or /usr/lib64 anymore, as instructed by (eselect )news item 2017-12-26-experimental-amd64-17-1-profiles, referencing https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout. Aka I use the new profile 17.1 and hence SYMLINK_LIB=no.
Comment 1 Navid Zamani 2018-03-12 18:03:17 UTC
Hello? Is anyone handling this?

I assumed this was trivial, but it seem it’s not, and this library is desperately needed for my homebanking software.
Comment 2 Navid Zamani 2018-03-12 18:25:56 UTC
Created attachment 523658 [details, diff]
SYMLINK_LIB_no.patch

Okay, I’ve made a patch myself.

It’s a hack. I simply made ./configure only look in lib64 paths instead of plain lib. Please don’t put it into Portage like that. Upstream should probably have a look at it too. (?)
Comment 3 Navid Zamani 2018-03-12 18:29:10 UTC
Created attachment 523660 [details]
libchipcard-5.0.2-r1.ebuild

Here’s the associated fixed ebuild.

I’ve just tested it, and it installs properly.

This will NOT work on a 32 bit system, btw.
(Though changing the patch to say 32 instead of 64, or ideally both, is trivial.)
Comment 4 Navid Zamani 2018-03-12 18:30:18 UTC
@Hanno Boeck: Can you give this the finishing touch, and put it into the Portage repository? (Before closing the bug.)
Comment 5 Larry the Git Cow gentoo-dev 2018-05-13 21:05:04 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f67f79ffa77621f100f2b9f7ef4f9c4f0bf6a66e

commit f67f79ffa77621f100f2b9f7ef4f9c4f0bf6a66e
Author:     Andreas Sturmlechner <asturm@gentoo.org>
AuthorDate: 2018-05-13 20:25:09 +0000
Commit:     Andreas Sturmlechner <asturm@gentoo.org>
CommitDate: 2018-05-13 21:04:49 +0000

    sys-libs/libchipcard: 5.0.4 version bump
    
    Bug: https://bugs.gentoo.org/648196
    Package-Manager: Portage-2.3.36, Repoman-2.3.9

 sys-libs/libchipcard/Manifest                 |  1 +
 sys-libs/libchipcard/libchipcard-5.0.4.ebuild | 45 +++++++++++++++++++++++++++
 2 files changed, 46 insertions(+)
Comment 6 Andreas Sturmlechner gentoo-dev 2018-05-13 21:06:26 UTC
Hi Navid, thanks for your report and patch, however the version bump should make this modification obsolete. Please test.