First of all the source tarball (unless it's been updated in March)
doesn't build at all on Ubuntu, because of a problem that some "cp"
commands refer to the wrong directories. I'm thinking maybe the
repository snapshot was taken when you guys were halfway through
changing what directories some files live in?
Anyhow the latest git repository version does build, but then io won't
run after it's built; it says:
io: error while loading shared libraries: libiovmall.so: cannot open
shared object file: No such file or directory
I think the problem is that the make process doesn't update the .so
cache, so when you try to run "io" it doesn't look in /usr/local/lib
for libiovmall.so. If you run io_static, that works, or if you
specify the load path manually with one of these two methods, these work:
/lib/ld-linux.so.2 --library-path /usr/local/lib /usr/local/bin/io
export LD_LIBRARY_PATH=.:/usr/local/lib:/usr/lib:/lib
But they aren't practical because neither fixes invocations of io from
scripts. However, running this command:
ldconfig
(with no arguments) seems to fix the problem. It's purpose is to
rebuild the shared library cache. So I'm thinking maybe the make
process (or install process) needs to run ldconfig? You have to run
it before you can compile any of the addons, because the rest of the
build process requires io already. Obviously if your machine
*already* had io building, then the libraries were set up right for
build N, so build N+1 is going to work for you too. So you will only
see this on a fresh machine.
Finally, I'm puzzled why you don't use autotools - autoconf and
automake? I use them on my current project and find them helpful.
It's really not that big a step from learning Makefiles to learning
autotools, and I think a ./configure script would really help with a
lot of the issues I've read on the mailing list about people having
trouble compiling on other OS's. Do you have a dislike of autotools,
or is it that no one has stepped up and done it? I see that you're
doing some magic halfway through the build process, with the first
half dedicated to building the vm, and once you have the core of io
built, then you turn around and have io "build itself" the rest of the
way. Is it that this magic build is not compatible with autotools,
making it difficult to port the Makefile to a Makefile.am?
.
