Hey Pete,

Thanks for the quick and helpful response.  I first tried
./configure --without-javadx;make, but it still tried to do javac,
so I chose the next easiest method, and edited java out of the
SUBDIRS in Makefile.  That worked, but now I have two more questions:

1:      When you invoke dx and click on the Samples button, by default
        it looks for samples in whatever the current directory was
        when you invoked it.  You can see the samples (which look
        very interesting) that were installed by changing the Filter
        field to read -

                /usr/local/dx/samples/programs/*.net

        Is there a way to change the default, so I don't have to tell
        everybody to manually change it to see the samples?

2:      I can't get the tutorial to work.  When I click on the Run Tutorial
        button, I get an empty window with File on the menu bar,
        with one option, Quit.

Peter Daniel Kirchner wrote:
Forwarded message:
> From [EMAIL PROTECTED]  Thu May  4 18:10:40 2000
> Date: Thu, 04 May 2000 18:42:09 -0400
> From: "Peter Daniel Kirchner" <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: Re: [opendx-dev] CLASSPATH and dxsamples
> Sender: [EMAIL PROTECTED]
> 
> Hi Tom,
> 
> Actually, we don't yet support kaffe for building javadx.  We took
> the javac -verbose route to automatically configuring the dx build
> which at the time precluded kaffe.  The dx configure leaves information
> for the dxsamples configure.  I bet we have not handled this correctly
> since this has changed in "dx" and we have not
> re-rolled a dxsamples tarball. Ouch.
> 
> Workaround #0: go to the dxsamples Makefile and remove java from the
> SUBDIRS.  The remaining might not work because of my oversight explained
> in the first paragraph:
> Workaround #1 : skip javadx, for dx, configure --without-javadx
> Workaround #2: install jdk 1.1.8, I think there is an RPM for same,
> my favorite though is the IBM jdk, it may want IBM_LINUX set and
> JAVA_ARCH set to linux (vs. genunix ).
> 
> If you want to try to make dx build with kaffe, start by setting
> CLASSPATH (KLASSPATH?) to /usr/share/kaffe/Klasses.jar  prior to dx
> configure, and take it from there.
> 
> I'll investigate the dx/dxsamples build coordination and try to
> get a fix in soon.  Thanks for the append.
> 
> Pete
> 
> "Tom G. Smith" wrote:
> 
> > Just got back from vde2000, and liked OpenDX well enough to try
> > installing it, which I've done, partly successfully, on a
> > RedHat 6.1 system.  I can get the dx command to run, and I
> > get the GUI window, but no samples.  So I tried the commands below
> > and get the errors shown.  Numerous guesses in changing CLASSPATH
> > hasn't helped.
> >
> >         tar xzf dxsamples-4.0.8.tar.gz
> >         chown -R root:root dxsamples-4.0.8
> >         chmod 755 dxsamples-4.0.8
> >         cd dxsamples-4.0.8
> >         find . -perm +2000 -exec chmod -s {} \;
> >         ./configure
> >         make # Gets errors, so to isolate -
> >         cd java/samples
> >
> > [dxsamples-4.0.8/java/samples]# make
> > javac AutoInsurance.java CCNet2.java GroceryList.java HomeOwn.java 
> > MRI_2.java MutualFund.java  ScatterData.java Streamline.java Topo.java 
> > ddi.java gordon.java hedge.java ibmqw.java npvcall.java optval.java 
> > wacc.java
> >
> > Could not initialize Kaffe.
> > It's likely that your CLASSPATH settings are wrong.  Please make sure
> > your CLASSPATH does not include any java.lang.* classes from other JVM
> > vendors, such as Sun's classes.zip, BEFORE Kaffe's Klasses.jar.
> > It is okay to have classes.zip AFTER Klasses.jar
> >
> > The current effective classpath is 
> > `/opt/netscape/java/classes/java40.jar:/usr/local/jdk117_v1a/lib/classes.zip:/usr/local/dx/java/htmlpages/dx.jar:.:/usr/share/kaffe/Klasses.jar:/usr/share/kaffe/comm.jar:/usr/share/kaffe/pjava.jar:/usr/share/kaffe/servlet.jar:/usr/share/kaffe/pizza.jar'
> > make: *** [samples.jar] Error 255

------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain 
privileged, confidential, or proprietary information that is exempt from 
disclosure under law.  If you have received this message in error, please 
inform us promptly by reply e-mail, then delete the e-mail and destroy any 
printed copy.   Thank you.

==============================================================================

Reply via email to