On 02/12/10 10:37 PM, Douglas E. Engert wrote:
Kevin Reinholz wrote:
On 2/12/10 7:16 AM, Douglas E. Engert wrote:
Ludovic Rousseau wrote:
2010/2/11 Douglas E. Engert <[email protected]>:
Replying to my own message, I did some more tests with 1.5.5
and ccid-1.3.11 and can get a bus error with these also.
I then did:
reboot with reader present.
Start pcscd -d -f
unplugged reader
plugged it back in
insert card
Got message about IFDHPowerICC() PowerUp failed
So reinserted the card.
run pkcs15-tool -r
pulled out card
inserted card
pulled out card
unplugged reader
got bus error.
So the bus error is not related to latest mods. but
still present.
I rebuild pcsc-lite using hotplug_libusb and I also have crashes if I
use electric-fence.
I don't think I have them if I use hotplug_libhal, but I will
double check.
Maybe the bug is in hotplug_libusb.
I am still looking too. Solaris does not have hal, so have to use
libusb.
For what it's worth, OpenSolaris (SunOS 5.11) does have HAL now so
that might be an interesting thing to test. I've built
pcsc-lite-1.5.5 and ccid-1.3.11 using Sun Studio 12 on SunOS 5.11 as
GCC choked on pcsc-lite under that platform.
Interesting, I have not had issues with gcc from Sun on Solaris 10.
%/usr/sfw/bin/gcc --version
gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
I've tried unsuccessfully to compile pcsc-lite-1.5.5 on OpenSolaris
using both gcc-3.4.3 and gcc-4.3.2:
reinh...@etrenank:~$ gcc --version
gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
reinh...@etrenank:~$ /usr/bin/gcc-4.3.2 --version
gcc-4.3.2 (GCC) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I tried various combinations of your suggested gcc compiler flags in
your posting here:
http://opensolaris.org/jive/message.jspa?messageID=457013#457013
Here's one such combo:
env CFLAGS="-g" CPPFLAGS="-DDEBUG" LDFLAGS="-g"
PTHREAD_CFLAGS="-pthreads" LIBUSB_CFLAGS="-I/usr/include"
LIBUSB_LDFLAGS="-L/usr/lib -lusb" CPPFLAGS="-D_TS_ERRNO"
LDFLAGS="-R/usr/local/lib:/usr/lib"
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --disable-libhal
--enable-libusb
But always receive the same linker error during gmake whether using
gcc-3.4.3 or gcc-4.3.2.
With gcc-3.4.3:
libtool: link: gcc -shared -Wl,-z -Wl,text -Wl,-h -Wl,libpcsclite.so.1
-o .libs/libpcsclite.so.1.0.0 .libs/libpcsclite_la-debug.o
.libs/libpcsclite_la-dyn_hpux.o .libs/libpcsclite_la-dyn_macosx.o
.libs/libpcsclite_la-dyn_unix.o .libs/libpcsclite_la-error.o
.libs/libpcsclite_la-winscard_clnt.o .libs/libpcsclite_la-strlcat.o
.libs/libpcsclite_la-strlcpy.o .libs/libpcsclite_la-sys_unix.o
.libs/libpcsclite_la-thread_unix.o .libs/libpcsclite_la-utils.o
.libs/libpcsclite_la-winscard_msg.o -R/usr/local/lib:/usr/lib
-R/usr/local/lib -L/usr/local/lib -ldl -lsocket -lc -pthreads
-pthreads -pthreads
Text relocation remains referenced
against symbol offset in file
SHMMessageSend 0x85e
.libs/libpcsclite_la-winscard_msg.o
SHMMessageSend 0x8b4
.libs/libpcsclite_la-winscard_msg.o
SHMMessageSend 0x8f6
.libs/libpcsclite_la-winscard_msg.o
SYS_GetSeed 0x4b0
.libs/libpcsclite_la-sys_unix.o
ld: fatal: relocations remain against allocatable but non-writable sections
collect2: ld returned 1 exit status
make[2]: *** [libpcsclite.la] Error 1
Or with gcc-4.3.2:
libtool: link: /usr/bin/gcc-4.3.2 -shared .libs/libpcsclite_la-debug.o
.libs/libpcsclite_la-dyn_hpux.o .libs/libpcsclite_la-dyn_macosx.o
.libs/libpcsclite_la-dyn_unix.o .libs/libpcsclite_la-error.o
.libs/libpcsclite_la-winscard_clnt.o .libs/libpcsclite_la-strlcat.o
.libs/libpcsclite_la-strlcpy.o .libs/libpcsclite_la-sys_unix.o
.libs/libpcsclite_la-thread_unix.o .libs/libpcsclite_la-utils.o
.libs/libpcsclite_la-winscard_msg.o -Wl,-rpath
-Wl,/usr/local/lib:/usr/lib -Wl,-rpath -Wl,/usr/local/lib
-L/usr/local/lib -ldl -lsocket -lc -pthreads -pthreads -pthreads
-Wl,-soname -Wl,libpcsclite.so.1 -o .libs/libpcsclite.so.1.0.0
Text relocation remains referenced
against symbol offset in file
SHMMessageSend 0x954
.libs/libpcsclite_la-winscard_msg.o
SHMMessageSend 0x9c6
.libs/libpcsclite_la-winscard_msg.o
SHMMessageSend 0xa19
.libs/libpcsclite_la-winscard_msg.o
GetDaemonPid 0x1a5
.libs/libpcsclite_la-utils.o
ld: fatal: relocations remain against allocatable but non-writable sections
collect2: ld returned 1 exit status
gmake[2]: *** [libpcsclite.la] Error 1
For good measure I also tried building pcsc-lite with, alternately, Gnu
LD and Sun's LD. The same linker error noted above occurred with both
versions of LD, specified during configure with the LD=/usr/gnu/bin/ld
flag try to the process with Gnu LD instead of the default Sun LD.
reinh...@etrenank:~$ /usr/bin/ld --version
ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1689
reinh...@etrenank:~$ /usr/gnu/bin/ld --version
GNU ld (GNU Binutils) 2.19
Copyright 2007 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later
version.
This program has absolutely no warranty.
But I used the disable-hal and enable-usb flags when I did it.
For kicks I also tried disabling libusb and enabling libhal. HAL is
recognized by configure with no problems:
checking for LIBHAL... yes
checking libhal.h usability... yes
checking libhal.h presence... yes
checking for libhal.h... yes
checking for libhal_ctx_new... yes
<snip>
libhal support: yes
libusb support: no
But gcc chokes at the same point during gmake.
It's interesting that compilation goes smoothly using the Sun Studio
compiler. Of course, most of the Sun-packaged Gnu software in
OpenSolaris was built using the Sun Studio compiler instead of gcc, so
it probably shouldn't be that surprising.
Do you have any problems when removing a reader? It turns out 1.5.5
has problems when removing a reader.
I also noted that I could remove the reader sometimes, but If I
reinserted
it in the same spot, pcscd would not see it. If I put it into a different
spot, usb/pcscd would see it as a new reader /n in the name would change.
I can try compiling these new betas on SunOS 5.11 and see what happens.
Thanks for the report.
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
