OK, thanks.
aclocal;autoheader;automake;autoconf;configure is the sequence I'm using,
and it isn't picking up the include files. I'm just going to kludge for now
by putting the appropriate headers into /usr/include or something.
The name of it doesn't matter right now. It will eventually become a .jar,
but I don't care about security right now. When we do the final thing it
will be a very small change.
I am not modifying the makefiles at all yet. I compiled classpath.zip
manually.
--John Keiser
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron
> M. Renn
> Sent: Wednesday, October 07, 1998 6:55 PM
> To: [EMAIL PROTECTED]
> Subject: Re: A Request
>
>
> John Keiser wrote:
> > Hey guys, I have classpath.zip all bundled up now (it's
> about 150K,
> > incidentally), and I'm just gonna leave it that way while I
> integrate with
> > Japhar.
>
> To go back to a suggestion someone made a long time ago, why not call it
> "glibj.jar"?
>
> If automake;autoconf;configure doesn't set things up for
> compiling, I don't
> know what will.
>
> --
> Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
>
>
