Trying to install libaio

[timfox]

When running JBM on the messaging lab it does not find AIO and uses NIO instead.

I tried to install libaio1 as per the instructions in the userguide and it complains there is no such library as libaio1.

I tried with libaio and it says this is already installed.

The user guide instructions (which I copied from the alpha) are wrong and need correcting, or users won't be able to use the AIO journal.

[clebert.suconic]

You also need to have ./trunk/native/bin on LD_LIBRARY_PATH. We should also document this.

export LD_LIBRARY_PATH=./path-to-trunk/native/bin

[timfox]

Yes, please document it. Otherwise users won't be able to use AIO.

[timfox]

Also you need to add it to the quick start guide.

[timfox]

I tried setting LD_LIBRARY_PATH and it makes no difference, still get

 [java] WARNING: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

[timfox]

AIO is already installed:

[xyz@blahblah ~]# sudo yum install libaio
Loaded plugins: rhnplugin, security
This system is not registered with RHN.
RHN support will be disabled.
Setting up Install Process
Parsing package install arguments
Package libaio-0.3.106-3.2.x86_64 already installed and latest version
Package libaio-0.3.106-3.2.i386 already installed and latest version
Nothing to do

[clebert.suconic]

Is that a different CPU or something? (don' t know.. like Itanium... maybe we need to recompile it there?)

[timfox]

AFAIK there are 2 main flavours of 64 bit x64 and itanium

[timfox]

This needs more thought. Before we release we need to make sure we have a .so compiled for each of the architectures that the Linux 2.6 is compiled for, and document them unambiguously.

[clebert.suconic]

We just need to compile them and add them to the binaries. I will do it first thing next week.

[timfox]

Cool.

We should have both AMD and Intel boxes in the qa lab somewhere, so should be ok.

If people want to compile for other architectures they can build from source. :)

[timfox]

Hmm, we should also probably build for IBM POWER chips too, these are popular in the data centre, i beleive.

we should also give instructions how to build from source in the user guide

[timfox]

We should make it explicit in the docs what architectures we support.

[timfox]

I also think LD_LIBRARY_PATH should be set in the run script. The user shouldn't have to do this.

It also needs to be set in the examples, or they'll never be using AIO.

[timfox]

I've added a small section on LD_LIBRARY_PATH to the docs, and I added it to run.sh.

Clebert - can you check this is correct?