We have a group of machines using a shared filestore so PCSC Lite and
all the drivers etc. are installed in /home/share/tools (as opposed to
the default of /usr/local) -- actually we use stow and so all the bits
are in their own directories in /home/share/tools/pkg and then get
stowed.

I believe there is a problem with the pcsc-tools installation.  The perl
scripts are fine, the issue is with the compilation of pcsc_scan:

gcc -Wall -O2 -DVERSION=\"`echo \`pwd\` | sed s/.*tools-//`\"   -c -o
pcsc_scan.o pcsc_scan.c
pcsc_scan.c:67:22: winscard.h: No such file or directory

Clearly the includes directory (in our case /home/share/tools/include)
should be included in the command line.  Also the location of the
libpcsclite.so (in our case /home/share/tools/lib) needs to be given. 
The following worked for me:

gcc -I/home/share/tools/include -Wall -O2 -DVERSION=\"`echo \`pwd\` |
sed s/.*tools-//`\"   -c -o pcsc_scan.o pcsc_scan.c

gcc -L/home/share/tools/lib  pcsc_scan.o  -lpcsclite -lpthread -o
pcsc_scan

By redefining CFLAGS and LDFLAGS:

CFLAGS = -I/home/share/tools/include -Wall -O2 -DVERSION=\"$(VERSION)\"
LDFLAGS = -L/home/share/tools/lib

but as to what the general solution should be I am not sure.


-- 
Russel.
====================================================================
Dr Russel Winder                    Chief Technology Officer
OneEighty Software Ltd              Tel: +44 20 8680 8712
Cygnet House                        Fax: +44 20 8680 8453
12-14 Sydenham Road                 [EMAIL PROTECTED]
Croydon, Surrey CR9 2ET, UK         http://www.180sw.com           
====================================================================
Under the Regulation of Investigatory Powers (RIP) Act 2000 together
with any and all Regulations in force pursuant to the Act One Eighty
Software Ltd reserves the right to monitor any or all incoming or
outgoing communications as provided for under the Act

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to