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]
RE: problem building tomcat 3.2.1 on Solaris x86
This problem comes up on the Ant (Ant is what is doing the build) mailing list somewhat frequently. It usually results in you adding the ant.jar file to the jdk/lib/ext directory. Otherwise, there is usually some jar file in there that the user added which make JavaC not work with ant any more. By the way, Tomcat is written in Java and distributed as .jar files, so you don't have to build it (you could if you want to, but its not necessary). Unless you want the latest from CVS. Randy -Original Message- From: Jennifer Dyess [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 14, 2001 1:36 PM To: [EMAIL PROTECTED] 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]
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]
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]
RE: problem building tomcat 3.2.1 on Solaris x86
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]
Re: problem building tomcat 3.2.1 on Solaris x86
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 com
RE: problem building tomcat 3.2.1 on Solaris x86
java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Java HotSpot(TM) Client VM (build 1.3.0, mixed mode) -Original Message- From: lee [mailto:lee]On Behalf Of lee fellows Sent: Wednesday, February 14, 2001 12:20 PM To: [EMAIL PROTECTED] Subject: Re: problem building tomcat 3.2.1 on Solaris x86 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 addi
Re: problem building tomcat 3.2.1 on Solaris x86
Hi Jennifer, Sorry, I had hoped to see something quckly. Unfortunately, I do not have a Solaris box to chase this further. Take a look in $JAVA_HOME/jre/lib. You should see two sub-directories: green_threads and classic. It sounds like the classic libraries are missing. I do not know if this has something to do with your version of Solaris on an x86 box or not. Seems there was some condition like that previously. Hopefully someone else can help you further. Jennifer Dyess wrote: java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Java HotSpot(TM) Client VM (build 1.3.0, mixed mode) -Original Message- From: lee [mailto:lee]On Behalf Of lee fellows Sent: Wednesday, February 14, 2001 12:20 PM To: [EMAIL PROTECTED] Subject: Re: problem building tomcat 3.2.1 on Solaris x86 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
Re: problem building tomcat 3.2.1 on Solaris x86
Jennifer, Another thing you may want to look at: Try downloading the jdk again from Sun and installing in a different directory, i.e., /usr/jdk1.3. It is possible something went wrong during your installation. lee fellows wrote: Hi Jennifer, Sorry, I had hoped to see something quckly. Unfortunately, I do not have a Solaris box to chase this further. Take a look in $JAVA_HOME/jre/lib. You should see two sub-directories: green_threads and classic. It sounds like the classic libraries are missing. I do not know if this has something to do with your version of Solaris on an x86 box or not. Seems there was some condition like that previously. Hopefully someone else can help you further. Jennifer Dyess wrote: java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Java HotSpot(TM) Client VM (build 1.3.0, mixed mode) -Original Message- From: lee [mailto:lee]On Behalf Of lee fellows Sent: Wednesday, February 14, 2001 12:20 PM To: [EMAIL PROTECTED] Subject: Re: problem building tomcat 3.2.1 on Solaris x86 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 com
Re: problem building tomcat 3.2.1 on Solaris x86
two suggestion, one from an earlier post 1. take a look at the build.sh script and see if it is setting any variables that may affect the classpath. play around with that. 2. Tomcat is Java based, you can download the already built jar files and use them directly 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 11:40 AM Subject: RE: problem building tomcat 3.2.1 on Solaris x86 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: [EM
