From: Don Smith <smithdc@UMDNJ.EDU>
To: Anthony Green <green@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: tomcat 4 jsp compilation status?
Date: Tue, 30 Apr 2002 06:53:00 -0000 [thread overview]
Message-ID: <3CCEA18A.1050807@umdnj.edu> (raw)
In-Reply-To: <1019925156.3282.6.camel@dhcppc2>
The latest problem with the install is that i get this error, since it
is around the --resource tag i was wondering if maybe this had something
to do with the syntax change
/mkinstalldirs `dirname
upstream/src/share/org/apache/jasper/resources/messages
.o`
gcj3 --resource `echo
upstream/src/share/org/apache/jasper/resources/messages.pr
operties | sed "s/.*\/src\/share\///g"` -o
upstream/src/share/org/apache/jasper/
resources/messages.o -c
upstream/src/share/org/apache/jasper/resources/messages.
properties
gcj3: cannot specify -o with -c or -S and multiple compilations
make: *** [upstream/src/share/org/apache/jasper/resources/messages.o]
Error 1
Anthony Green wrote:
>On Fri, 2002-04-26 at 13:33, Don Smith wrote:
>
>
>>What's the status of a gcj version of tomcat that can support jsps?
>>Is it possible, if not what needs to be done?
>>
>>
>
>It's been a while since I looked at that (even though it would be really
>cool to get this working).
>
>When I did start looking at it, I went about it the wrong way -- setting
>up tomcat to compile the jsp code to .so immediately. Unfortunately,
>tomcat has many built in assumptions about the compiler generating
>.class files which it then manipulates (or just moves around, I think).
>
>It makes better sense to do this in baby steps. First get tomcat to
>compile jsp code to bytecode with 'gcj -C' and have everything work with
>the gcj interpreter.
>
>Once that all works, perhaps we can figure out a good way to compile the
>.class files to .so. I'm thinking this should be an extra step once the
>.class file is copied into the desired location by tomcat.
>
>It would be great if somebody (like you!) could spend a little time
>trying to get this to work. I'd be happy to help this person (like
>you!) along.
>
>AG
>
>
>
next prev parent reply other threads:[~2002-04-30 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 13:36 Don Smith
2002-04-27 19:24 ` Anthony Green
2002-04-29 6:56 ` Don Smith
2002-04-29 7:08 ` Anthony Green
2002-04-29 13:06 ` Don Smith
2002-04-29 13:25 ` Anthony Green
2002-04-30 6:53 ` Don Smith [this message]
2002-04-30 7:25 ` Anthony Green
[not found] ` <3CCEB932.304@umdnj.edu>
[not found] ` <1020181846.1858.47.camel@dhcppc2>
[not found] ` <87d6whaza6.fsf@creche.redhat.com>
2002-04-30 11:17 ` --resource problems (Was: tomcat jsp compilation status?) Anthony Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CCEA18A.1050807@umdnj.edu \
--to=smithdc@umdnj.edu \
--cc=green@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).