How to compile CAC (Command Access Card) for DOD website?

[Hedgehog]

I am having problems compiling the files required for the cac reader. Here are the directions.

I have Pupeee 301 on the internal card on the 4gig Eeepc with 1gig ram

http://symbolik.wordpress.com/2007/02/2 ... -on-linux/

I am running into errors, I have never compiled before, so not understanding the error. I also cant copy and paste from the console to show you the errors

Can anybody try to compile these?.

I have devx set up, and it starts compiling, but something is going wrong in the make process.

[muggins]

Copy & paste from console is as easy as dragging cursor, over whatever you want to copy, then to paste, either Control+v, Shift+insert, or middle mouse click.

[Hedgehog]

OK, here is the code on the first compile try of libusb.

Thanks in advance for your help

Code: Select all

# cd libusb-0.1.12 && /configure -prefix=/usr/cac && make && make install
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking platform type: ... UNIX/LINUX
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether ln -s works... yes
checking for uncompress in -lz... yes
checking for dlopen in -ldl... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PCSC... /configure: line 19830: 1: command not found
configure: WARNING: pcsc-lite not found
/configure: line 19942: enable_pk11install: command not found
configure: WARNING: skipping pk11install
checking for ANSI C header files... (cached) yes
checking for string.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking whether lstat dereferences a symlink specified with a trailing slash... yes
checking whether stat accepts an empty string... no
checking for vprintf... yes
checking for _doprnt... no
checking for memset... yes
checking for strdup... yes
checking for strerror... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING:  Makefile.in seems to ignore the --datarootdir setting
config.status: creating src/libckyapplet/Makefile
config.status: creating src/libckyapplet/libckyapplet.pc
config.status: creating src/coolkey/Makefile
config.status: creating src/install/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
make  all-recursive
make[1]: Entering directory `/root/libusb-0.1.12'
Making all in .
make[2]: Entering directory `/root/libusb-0.1.12'
if /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H   -I.  -Werror  -g -O2 -MT usb.lo -MD -MP -MF ".deps/usb.Tpo" -c -o usb.lo usb.c; \
        then mv -f ".deps/usb.Tpo" ".deps/usb.Plo"; else rm -f ".deps/usb.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT usb.lo -MD -MP -MF .deps/usb.Tpo -c usb.c  -fPIC -DPIC -o .libs/usb.o
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT usb.lo -MD -MP -MF .deps/usb.Tpo -c usb.c -o usb.o >/dev/null 2>&1
if /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H   -I.  -Werror  -g -O2 -MT error.lo -MD -MP -MF ".deps/error.Tpo" -c -o error.lo error.c; \
        then mv -f ".deps/error.Tpo" ".deps/error.Plo"; else rm -f ".deps/error.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c  -fPIC -DPIC -o .libs/error.o
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c -o error.o >/dev/null 2>&1
if /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H   -I.  -Werror  -g -O2 -MT descriptors.lo -MD -MP -MF ".deps/descriptors.Tpo" -c -o descriptors.lo descriptors.c; \
        then mv -f ".deps/descriptors.Tpo" ".deps/descriptors.Plo"; else rm -f ".deps/descriptors.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT descriptors.lo -MD -MP -MF .deps/descriptors.Tpo -c descriptors.c  -fPIC -DPIC -o .libs/descriptors.o
 gcc -DHAVE_CONFIG_H -I. -Werror -g -O2 -MT descriptors.lo -MD -MP -MF .deps/descriptors.Tpo -c descriptors.c -o descriptors.o >/dev/null 2>&1
/bin/sh ./libtool --mode=link gcc -Werror  -g -O2   -o libusb.la -rpath /usr/cac/lib -version-info @LT_CURRENT@:@LT_REVISION@:@LT_AGE@ -release @LT_RELEASE@ -export-dynamic   usb.lo error.lo descriptors.lo   -ldl -lz 
libtool: link: CURRENT `@LT_CURRENT@' is not a nonnegative integer
libtool: link: `@LT_CURRENT@:@LT_REVISION@:@LT_AGE@' is not valid version information
make[2]: *** [libusb.la] Error 1
make[2]: Leaving directory `/root/libusb-0.1.12'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/libusb-0.1.12'
make: *** [all] Error 2

[Hedgehog]

also cant get libusb-0.1.12.pet to install

EDIT well, i guess libusb is already installed, so must be my problem, the Eeepc is all USB interface

[Billwho?]

Hi Hedgehog
I can't help with your current problems but just for future reference. If at any time you need to copy the out put of a terminal and the top has scrolled out of the buffer. Meaning you are unable to highlight it to copy and paste it. Try this

Code: Select all

 ./configure | tee config_results.txt 

The tee command will create the text file config_results.txt and will echo any output from the terminal into the file which can then be attached to your posts. Or you can open the text file in Geany etc and the relevant information copied for posting in the usual way.