Jennifer,
You do not need the java/lib directories in your PATH. It should have
directories with
executables, not libraries.
Question: When you run java -version, what do you get?
Jennifer Dyess wrote:
>
> ok, I modified my classpath as you suggested:
> /usr/java/jre/lib/ext/jaxp.jar:/usr/java/jre/lib/ext/jcert.jar:/usr/java/jre
> /lib/ext/jnet.jar:/usr/java/jre/lib/ext/jsse.jar:/usr/java/jre/lib/ext/parse
> r.jar:/usr/java/jre/lib/ext/ant.jar:/usr/java/jre/lib/ext/servlet.jar:/usr/j
> ava/lib/tools.jar:.:
>
> what should the path look like? Here's min:
> :/usr/local/bin:/usr/local/sbin:/usr/ccs/bin:/usr/sbin:/usr/bin:/usr/java/bi
> n:/usr/java/lib/:/usr/java/jre/lib
>
> But, I still get the same error msg :(
>
> -----Original Message-----
> From: John Golubenko [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 10:54 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: problem building tomcat 3.2.1 on Solaris x86
>
> by the way, why do you have /usr/java/bin: xx/xx: in CLASSPATH? The
> directories should be
> in PATH, not CLASSPATH. The jars,or files should be in CLASSPATH (*.xx).
> This may cause the problems.
>
> -----Original Message-----
> From: Jennifer Dyess [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 11:01 AM
> To: [EMAIL PROTECTED]
> Subject: RE: problem building tomcat 3.2.1 on Solaris x86
>
> Thanks for the quick response!
>
> I'm running the Java 2 SDK Std Edition v 1.3
>
> No, I did not have the tools.jar in my classpath. I just added it, but I
> still get the same error.
> Here's my classpath:
> /usr/java/bin:/usr/java/lib:/usr/java/jre/lib:/usr/java/jre/lib/ext/jaxp.jar
> :/usr/java/jre/lib/ext/jcert.jar:/usr/java/jre/lib/ext/jnet.jar:/usr/java/jr
> e/lib/ext/jsse.jar:/usr/java/jre/lib/ext/parser.jar:/usr/java/jre/lib/ext/an
> t.jar:/usr/java/jre/lib/ext/servlet.jar:/usr/java/lib/tools.jar:.:
>
> Any other suggestions?
>
> -----Original Message-----
> From: Filip Hanik [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 14, 2001 10:28 AM
> To: [EMAIL PROTECTED]
> Subject: Re: problem building tomcat 3.2.1 on Solaris x86
>
> what version of the SDK do you have?
> also do you have $JAVA_HOME/lib/tools.jar in your CLASSPATH?
>
> Filip
>
> ~
> Namaste - I bow to the divine in you
> ~
> Filip Hanik
> Software Architect
> [EMAIL PROTECTED]
> www.filip.net
> ----- Original Message -----
> From: "Jennifer Dyess" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, February 14, 2001 10:35 AM
> Subject: problem building tomcat 3.2.1 on Solaris x86
>
> > I'm having a problem building TomCat v321 on a Solaris x86 intel box.
> >
> > I receive the error "cannot use classic compiler..."
> >
> > I've got the java2 sdk installed. The path to javac is in my
> > path/classpath. I can type javac from any dir and it appears to be
> > available.
> >
> > Searching thru the mail archives, I found a bug had been filed on this
> exact
> > problem, but on linux. Unfortunately, there was no
> > fix/workaround/resolution. Here's a link to the bug:
> > http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg04248.html
> >
> >
> >
> > bash-2.03# ./build.sh
> > Searching for build.xml ...
> > Buildfile: /usr/pkgs/jakarta-tomcat-3.2.1-src/build.xml
> >
> > prepare:
> > [copy] Copying 1 files to /usr/pkgs/build/tomcat/conf
> >
> > tomcat:
> > [javac] Compiling 217 source files to /usr/pkgs/build/tomcat/classes
> >
> > BUILD FAILED
> >
> > /usr/pkgs/jakarta-tomcat-3.2.1-src/build.xml:94: Cannot use classic
> > compiler, as
> > it is not available
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> NOTICE: This communication may contain confidential or other privileged
> information. If you are not the intended recipient, or believe that you
> have received this communication in error, please do not print, copy,
> retransmit, disseminate, or otherwise use the information. Also, please
> indicate to the sender that you have received this email in error, and
> delete the copy you received. Any communication that does not relate to
> official Columbia business is that of the sender and is neither given nor
> endorsed by Columbia. Thank you.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
