installation issues

[GoogleCodeExporter]

For which program(s) you want a new feature?
(Capacitor)

Which build of the program(s)?
FluxCapacitor-v1.2-j1.5

What operating system you use?
(unix64)

What steps will reproduce the problem?
Not a problem.
I asked our local systems people for help in settnig up fluxcapacitor and
this is what they consider to be an optimal way for someone who doesn't
have super-user access to set it up. You might like to change the
installation instructions to include some of this.

This is what he says:

It works fine on our existing systems, as long as you rebuild the  
shared libraries for the native methods.  It looks as though you were  
most of the way there.  Here's what I did:

1)  Rebuild the dynamic shared objects, and copy them to the correct  
location:

     cd FluxCapacitor-v1.2-j1.5
     pushd source/lpsolve55/lp_solve_5.5
     make clean
     make
     cp lpsolve55/*.so ../../../lib/native/lpsolve55/unix/x86/64
     popd
     pushd source/lpsolve55/lp_solve_5.5_java/lib/linux
     ./build
     cp *.so ../../../../../lib/native/lpsolve55/unix/x86/64
     popd

2)  Change the bin/flux.sh wrapper script to be a bit smarter.  Here's  
my version, flux.bash:

#!/bin/bash
FLUXPATH=$(dirname $(dirname $0))
case $(uname -m) in
   i386|i686) FLUXLIBS=$FLUXPATH/lib/native/lpsolve55/unix/x86/32 ;;
   x86_64 ) FLUXLIBS=$FLUXPATH/lib/native/lpsolve55/unix/x86/64 ;;
esac

java -Xmx1500M -XX:+AggressiveHeap -Djava.library.path="$FLUXLIBS" - 
jar "$FLUXPATH/lib/FluxCapacitor.jar" $@

then chmod +x flux.bash

As you can see, you don't need to mess with LD_LIBRARY_PATH at all -  
java.library.path does that on its own.

Original issue reported on code.google.com by g...@sanger.ac.uk on 20 Aug 2009 at 3:27

[GoogleCodeExporter]

Hi,

thank you for your detailed report! It is good to have as many such experiences 
that 
help people to orientate, therefore I posted this thread also in the forum

http://fluxcapacitor.wikidot.com/forum/t-177293/compiling-on-a-unix-64bit-platfo
rm-
with-a-custom-wrapper-script

Find also my comments on your protocol there - maybe you could tell me your 
*NIX 
platform to find out why the precompiled 64bit library did not work for you. It 
is 
not necessary to log into the forum to post, and I think it is a better area to 
discuss the topic there.

I am closing the issue (here).

Original comment by gmicha@gmail.com on 20 Aug 2009 at 5:20

• Changed state: Done
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by gmicha@gmail.com on 20 Aug 2009 at 5:22

• Added labels: Capacitor

[GoogleCodeExporter]

The operating system I am running is Debian Etch on 64-bit machines.

Original comment by g...@sanger.ac.uk on 21 Aug 2009 at 8:51