RE: SableVM on AIX 5.2 [was: Re: Help Solicited]

Hi

I downloaded the libffi from http://voxel.dl.sourceforge.net/sourceforge/pyobjc/libffi-src-20030921.tar.gz but when I run configure on to it, it complains that install-sh is not found.

The problem is that the default srcdir is . and the libfi_basedir is being taken as ..

So it serches for the file in ../ and ./.. directoris only.

If I set up the PATH as $PATH:.. and create a temporary subdirectory and run under directory for libffi (where configure is there) and run the configure from this subdirectory, the script executes properly but the Makefile being created is of 0 bytes only.

The output of the configure command for the libffi is attched for reference.

Any body can tell me the probable cause?

Also I have faced the same issue with building the Sable VM also when I tried from a sub directory.


Regards
Manish Sood




-----Original Message-----
From: Grzegorz B. Prokopski [mailto:[email protected]]
Sent: Sunday, November 21, 2004 1:19 AM
To: SableVM Users Mailing List
Subject: SableVM on AIX 5.2 [was: Re: Help Solicited]


Hello Manish,

On Fri, 2004-11-19 at 07:44, Manish.Sood wrote:
> I need to install Sable 1.1.6 on AIX 5.2.
> I have downloaded the souces sablevm-1.1.6.tar.gz and
> sablevm-classpath-1.1.6.tar.gz and expanded them. 

Actually 1.1.7 is our latest release, but at this stage solving your
problems with compilation of 1.1.6 will be the same as with 1.1.7.

> But when I try to build the SableVM, the configure complaints
> about the missing libffi. The output of the configure is attached
> for reference.

Libffi (unfortunatelly) comes with sources for gcc, but it is not
required to compile them all just to get libffi installed on your
system.  In newer gcc (3.4 and up, I think) you can just do 'configure
&& make install' in gcc/libffi directory of unpacked gcc sources.
For older versions you should follow

	http://sablevm.org/wiki/LibFFI

It also describes how to setup your environment so that libffi was
"picked up" during compilation and later, when you run SableVM.

Note, that you should be using rather new version of GCC to compile
libffi.  It does not have to match exactly the version of GCC soures
from which you taken the libffi sources, but should be "similarly
recent".  I.e. you probably won't be able to compile libffi from
gcc 3.3 using gcc 2.95.  What version of gcc did you use?

> Kindly let me know where I can get the source/binaries for the
> required libraries and how should I build them (libffi, libpopt,
> libgtk, libart and libldl3).

I don't know where people usually get binaries for AIX, but you should
have no problem with finding the needed sources IF you cannot find
precompiled binaries.

ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x/popt-1.7.tar.gz
libldl3 comes with libtool ('ldl' is Libtool Dynamic Linker or so, IIRC)

libgtk - http://www.gtk.org/download/ - use version 2.4
libart - ftp://ftp.gnome.org/pub/GNOME/sources/libart_lgpl/2.3/

Note that these libraries might have some build or runtime dependencies
themselves, so it'd be *much* faster/easier for you to just find
precompiled versions.  In particular libgtk and libart will be included
in any distribution of GNOME desktop (probably also with libpopt).

> Also I need to know which version of jikes is required and how should
> it be put to use i.e. putting the path to jikes executable is enough??

We use the latest version Jikes 1.22 but "slightly" older versions also
are expected to work (so if you already have a precompiled binary of
jikes you should first try it on, and only compile newer versions if the
older one didn't work).

> Also the should I use make or gmake to build SableVM?

GNU Make, that is 'gmake'.

> I also need to copy the Makefile.in to makefile before issueing the make
                 ^^^^^
> command (either make or gmake) BUT the make fails as it complaints 
> 		makefile:15: *** missing separator.  Stop.

No!  You should run ./configure script that will generate all needed
Makefiles.  Usually the configure call, for the "first time" compilation
of sablevm would look like:

./configure --enable-debugging-features --prefix=/where/to/install

for sablevm-classpath you omit the --enable-debugging-features, but
the --prefix value *has to be the same*.

Hope this helps,

				Grzegorz B. Prokopski
-- 
Grzegorz B. Prokopski      <[email protected]>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://sablevm.org/wiki/Features



_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user

_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user