08-25-2012
Have you set the variables "LD_LIBRARY_PATH" and "LIBPATH" both to the respective locations?
Some programs from the Solaris/Linux world expect $LD_LIBRARY_PATH to evaluate to the library location and don't care for the AIX pendant $LIBPATH, which is why it is a good safety measure to set both.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. Programming
hello all
I want to work in shared libraries how can i work in
Linux Environment ? (2 Replies)
Discussion started by: rajashekaran
2 Replies
2. UNIX for Advanced & Expert Users
What is the primary difference between static library and dynamic library?
and how to write static shared library? (1 Reply)
Discussion started by: areef4u
1 Replies
3. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
4. Programming
Hello,
On a Centos 5.0 box, I have two versions of a library (sqlite):
(1) in /usr/lib that was installed using yum (maybe from php but I am not really sure)
(2) in /usr/local/lib that I installed myself by compiling from the source code.
My C++ program contains the following lines:
... (12 Replies)
Discussion started by: JCR
12 Replies
5. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
6. HP-UX
I have never seen this issue before, but here is what is happening. I link an executable against two dynamic mlib libraries veclib and lapack. We place a newer version of these libraries in a write only directory and point the shlib_path at that directory. When the executable runs, it gets a... (3 Replies)
Discussion started by: sambarusty
3 Replies
7. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
8. OS X (Apple)
I'm trying to get Valgrind to work with an openmpi application in OS X. However I want to hardcode the path to a shared library called libmpiwrap-amd64-darwin.so into my application so that it is available at runtime. In Linux this is relatively simple, I would just add the option... (0 Replies)
Discussion started by: Valgrinder
0 Replies
9. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
10. Linux
Hi All,
i am facing shared library error, below is the output of the command I am executing on my client
# /usr/software/bin/sudo
/usr/software/bin/sudo: error while loading shared libraries: libaudit.so.1: cannot open shared object file: No such file or directory
#
I tried install... (4 Replies)
Discussion started by: muzaffar.k
4 Replies
LEARN ABOUT CENTOS
reader.conf
READER.CONF(5) PC/SC Lite READER.CONF(5)
NAME
reader.conf - configuration file for pcscd readers' drivers
DESCRIPTION
The /etc/reader.conf.d/reader.conf file contains configuration information for serial and (some) PCMCIA smart card readers.
USB readers SHALL NOT be configured using this file. pcscd uses another mechanism to automatically load USB drivers.
SYNTAX
The /etc/reader.conf.d/reader.conf is a regular text file. Each reader must be defined by four fields:
FRIENDLYNAME TEXT_STRING
DEVICENAME FILENAME
LIBPATH FILENAME
CHANNELID NUMBER
The "FRIENDLYNAME" field is an arbitrary text used to identify the reader. This text is displayed by commands like pcsc_scan(1) that prints
the names of all the connected and detected readers.
The "DEVICENAME" field was not used for old drivers (using the IFD handler version 2.0 or earlier). It is now (IFD handler version 3.0)
used to identify the physical port on which the reader is connected. This is the device name of this port. It is dependent of the OS ker-
nel. The first serial port device is called /dev/ttyS0 under Linux and /dev/cuaa0 under FreeBSD.
The "LIBPATH" field is the filename of the driver code. The driver is a dynamically loaded piece of code (generally a drivername.so*file).
The "CHANNELID" is no more used for recent drivers (IFD handler 3.0) and has been superseded by "DEVICENAME". If you have an old driver
this field is used to indicate the port to use. You should read your driver documentation to know what information is needed here. It
should be the serial port number for a serial reader.
EXAMPLE
# Gemplus GemPCTwin reader with serial communication
# connected to the first serial port
FRIENDLYNAME "GemPCTwin serial"
DEVICENAME /dev/ttyS0
LIBPATH /usr/lib64/pcsc/drivers/serial/libccidtwin.so.0.4.1
CHANNELID 1
DEBUGGING
In order to set up your /etc/reader.conf.d/reader.conf file correctly you may want to have debug messages from pcscd. I recommend you to
start pscsd in the foreground and debug mode using:
# pcscd --foreground --debug
If everything seems OK you can use the pcsc_scan command to print the list of correctly detected readers and try to get the ATR of your
smart cards.
AUTHOR
Ludovic Rousseau <ludovic.rousseau@free.fr>
SEE ALSO
pcscd(8), pcsc_scan(1)
Muscle August 2005 READER.CONF(5)