Scratch that ... I just noticed something else you said in that message.
The behaviour you are seeing would definitely arise if --classpath did not
work in japhar. Best check that.
--John Keiser
> -----Original Message-----
> From: John Keiser [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 24, 1998 5:37 PM
> To: Brian Jones; [EMAIL PROTECTED]
> Subject: RE: make dist and make distdir
>
>
> As long as the file java/net/InetAddress.class exists, that
> statement should
> work (japharh does not require a running Java class library, I believe).
> See if the java/net directory is getting compiled first or not ...
> --John Keiser
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Brian Jones
> > Sent: Thursday, September 24, 1998 3:09 PM
> > To: [EMAIL PROTECTED]
> > Subject: make dist and make distdir
> >
> >
> > I'm having problems with 'make dist' and 'make distdir'. Here is the
> > error message.
> >
> > make[2]: Entering directory `/usr/home/brian/classpath/native/java.net'
> > japharh --classpath ../.. --stubs --d . java.net.InetAddress
> > Unable to load class java.net.InetAddress
> > make[2]: *** [java_net_InetAddress_stubs.c] Error 1
> > make[2]: Leaving directory `/usr/home/brian/classpath/native/java.net'
> > make[1]: *** [distdir] Error 1
> > make[1]: Leaving directory `/usr/home/brian/classpath/native'
> > make: *** [distdir] Error
> >
> > This is after I changed native/java.net/Makefile.am to use the double
> > dashes with japharh (not sure if that is fixed in current japhar or
> > not) and reran automake, autoconf, and configure from the toplevel
> > directory. I'm not quite sure if this "japharh..." command should be
> > run when creating a distribution. Anyone know how to fix this?
> >
> > Brian
> > --
> > |-------------------------------|Software Engineer
> > |Brian Jones |[EMAIL PROTECTED]
> > |[EMAIL PROTECTED] |http://www.nortel.net
> > |http://www.classpath.org/ |------------------------------
> >
> >
>
>
