Re: [Chicken-users] libsvm egg install problem

2008-06-03 Thread Tom Poliquin
Dashi,

I messed up.

I dumbly used the 'svm-predict' example without
creating a model file!
So it looks like that is what caused the segfault.

I used your other example (svm-train), which
was well behaved but gave me the error shown
below.

I'll try to get some time in the next day or two
to create a real dataset and play with it a bit.

Looks like it's installed Ok ..

Thanks for the help and I'll update you
with my results.

Tom


Error using svm-train example:

CHICKEN
(c)2008 The Chicken Team
(c)2000-2007 Felix L. Winkelmann
Version 3.1.0 - linux-unix-gnu-x86  [ manyargs dload ptables applyhook ]
SVN rev. 10106  compiled 2008-05-20 on giliath (Linux)

; loading svm.scm ...
; loading /home/cowboyneal/lib/chicken/3/libsvm.so ...
; loading /home/cowboyneal/lib/chicken/3/libsvm_core.so ...
Error: libsvm: invalid data length

Call history:

syntax(define model (svm-train (new-svm-problem 
labels
 data) (new-svm-parameter)))
syntax(##core#set! model (svm-train (new-svm-problem 
l
abels data) (new-svm-parameter)))
syntax(svm-train (new-svm-problem labels data) 
(new-sv
m-parameter))
syntax(new-svm-problem labels data)
syntax(new-svm-parameter)
eval  (svm-train (new-svm-problem labels data) 
(new-svm-parame
ter))
eval  (new-svm-problem labels data)
libsvm.scm: 122  error  --


 Dashi,

 Thanks for the reply .. and sorry for my delay
 (startup deadline) ..

  Tom Poliquin wrote:
   I'm trying to install the libsvm egg and not
   having much success.
 
  I've updated the egg (v1.1), which hopefully works fine.
  Please give it a try.

 I tried it out and still having difficulties (albeit different ones :-) )

 Here's the output of chicken-setup ..

 --
 [EMAIL PROTECTED] chicken]$ chicken-setup libsvm

 The extension libsvm does not exist.
 Do you want to download it ? (yes/no/abort) [yes] yes
 downloading libsvm.egg from (www.call-with-current-continuation.org eggs/3
 80) gzip -d -c /tmp/chicken-setup-3-cowboyneal/downloads/libsvm.egg | tar
 xf - /home/cowboyneal/bin/csc -feature compiling-extension -s -O2
 libsvm_core.scm l
 ibsvm_core_wrap.c -lsvm -I/usr/include/libsvm-2.0/libsvm
   /home/cowboyneal/bin/csc -feature compiling-extension -s -O2 libsvm.scm
 Warning: extension `libsvm_core' is currently not installed
   rm -fr /home/cowboyneal/lib/chicken/3/libsvm.so
   cp -r libsvm.so /home/cowboyneal/lib/chicken/3/libsvm.so
   chmod a+r /home/cowboyneal/lib/chicken/3/libsvm.so
   rm -fr /home/cowboyneal/lib/chicken/3/libsvm_core.so
   cp -r libsvm_core.so /home/cowboyneal/lib/chicken/3/libsvm_core.so
   chmod a+r /home/cowboyneal/lib/chicken/3/libsvm_core.so
 --

 I ran it and got an undefined symbol .. __cxa_pure_virtual

 --
 [EMAIL PROTECTED] ~]$ csi svm.scm

 CHICKEN
 (c)2008 The Chicken Team
 (c)2000-2007 Felix L. Winkelmann
 Version 3.1.0 - linux-unix-gnu-x86      [ manyargs dload ptables applyhook
 ] SVN rev. 10106  compiled 2008-05-20 on giliath (Linux)

 ; loading svm.scm ...
 ; loading /home/cowboyneal/lib/chicken/3/libsvm.so ...
 ; loading /home/cowboyneal/lib/chicken/3/libsvm_core.so ...
 Error: (load) unable to load compiled module
 /home/cowboyneal/lib/chicken/3/libsvm_core.so
 /home/cowboyneal/lib/libsvm.so.1: undefined symbol: __cxa_pure_virtual
 --

 I dug around the Internet a bit and found it might be related
 to libsupc++ so I edited the libsvm egg build to add it, see below.
 (again I'm not an expert at this stuff).

 I reran the setup (by untarring the egg and running chicken-setup)
 and got ..

 --
 [EMAIL PROTECTED] libsvm]$ chicken-setup
   /home/cowboyneal/bin/csc -feature compiling-extension -s -O2
 libsvm_core.scm libsvm_core_wrap.c -lsvm -lsupc++
 -I/usr/include/libsvm-2.0/libsvm /home/cowboyneal/bin/csc -feature
 compiling-extension -s -O2 libsvm.scm rm -fr
 /home/cowboyneal/lib/chicken/3/libsvm.so
   cp -r libsvm.so /home/cowboyneal/lib/chicken/3/libsvm.so
   chmod a+r /home/cowboyneal/lib/chicken/3/libsvm.so
   rm -fr /home/cowboyneal/lib/chicken/3/libsvm_core.so
   cp -r libsvm_core.so /home/cowboyneal/lib/chicken/3/libsvm_core.so
   chmod a+r /home/cowboyneal/lib/chicken/3/libsvm_core.so
   chmod a+r /home/cowboyneal/lib/chicken/3/libsvm.setup-info
 --

 All seemed well until I ran the test code ..
 which ended with a SegFault.

 --
 [EMAIL PROTECTED] ~]$ csi svm.scm
 CHICKEN
 (c)2008 The Chicken Team
 (c)2000-2007 Felix L. Winkelmann
 Version 3.1.0 - linux-unix-gnu-x86      [ manyargs dload ptables applyhook
 ] SVN rev. 10106  compiled 2008-05-20 on giliath (Linux)
 ; loading svm.scm ...
 ; loading /home/cowboyneal/lib/chicken/3/libsvm.so ...
 ; loading /home/cowboyneal/lib/chicken/3/libsvm_core.so ...
 Segmentation fault
 --

 Looks like 

Re: [Chicken-users] Minor problem with cmake-based chicken build on cygwin

2008-06-03 Thread felix winkelmann
On Tue, Jun 3, 2008 at 2:38 AM, Nathan Thern [EMAIL PROTECTED] wrote:

 Thanks, Felix. So how does the chicken development team handle
 platform portability?


We have multiple Makefile-fragments and configure the build
via variables set on the command line, for example:

make PLATFORM=linux DEBUGBUILD=1

Writing our own makefiles in the end gives us more control. The CMake-based
build turned out to require lots of workarounds due to CMake limitations.
Additionally, it seems that users and contributers find it easier to submit
improvements.


cheers,
felix


___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Minor problem with cmake-based chicken build on cygwin

2008-06-03 Thread Elf


Felix,

I'm almost done with the new make system and compatibilities code for the 
various supported systems.  :)


-elf

On Tue, 3 Jun 2008, felix winkelmann wrote:


On Tue, Jun 3, 2008 at 2:38 AM, Nathan Thern [EMAIL PROTECTED] wrote:


Thanks, Felix. So how does the chicken development team handle
platform portability?



We have multiple Makefile-fragments and configure the build
via variables set on the command line, for example:

make PLATFORM=linux DEBUGBUILD=1

Writing our own makefiles in the end gives us more control. The CMake-based
build turned out to require lots of workarounds due to CMake limitations.
Additionally, it seems that users and contributers find it easier to submit
improvements.


cheers,
felix


___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users




___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users