"Aaron M. Renn" <[EMAIL PROTECTED]> writes:
> Brian Jones ([EMAIL PROTECTED]) wrote:
> > > -- Needed to mkdir vm/current and include, run autoheader without errors.
> > >
> > > -- Oops, as it turns out, we are supposed to symlink to vm/current
> > > during the build process. I deleted the dir and hand crancked the link.
> >
> > Okay, configure should have done the symlink for you, some sort of problem?
>
> If the link doesn't already exist, autoheader bombs, and you need to run
> autoheader before configure.
Okay, I'll switch that Makefile back to some sort of if Japhar, else
if Kaffe, else type statement which won't bomb. I don't know of a way
to let autoheader deal with a symlink created a configure time.
> > > -- Two compile errors in the GTK peers. These are bugs that need to be
> > > fixed. The error text is below:
> >
> > I compiled earlier today without the problems you mention. Could it
> > be javah in 1.1.5 is messed up? I'm using 1.1.7B.
>
> Could be. I'll look into it.
>
> > > For the record, my configure command was:
> > >
> > > ./configure --with-japhar --with-java=/usr/local/jdk1.1.5/bin/java \
> > > --with-javah=/usr/local/jdk1.1.5/bin/javah --with-jikes \
> > > --enable-maintainer-mode --with-classlib=/usr/local/jdk1.1.5/lib/classes.zip
> > >
> > > Now I'm off to see what happens when I type "make install" :-)
> >
> > Been playing with that today. I don't know if you did your get after
> > my last commit or not but you might want to try again just to see
> > those changes to where we install which in your case might be
> > something like /usr/local/japhar/lib/classpath,
> > /usr/local/japhar/share/classpath/glibj.zip. I haven't tried yet so I
> > may have made a mistake.
>
> make install worked great, and I've got Japhar working with the latest
> Classpath from CVS. The only problem I had was the the library names
> we use don't seem to work with Japhar even though Toshok claims they
> should. I had to create symlinks to the libjaphar_%s.so format to make
> it work. Otherwise, A-OK.
Chris is apparently going to look into this today.
Brian
--
Brian Jones <[EMAIL PROTECTED]>
