I didn't have much more luck with gcc on my Redhat 6.2 system.
mod_webapp in the distro is just incomplete. It was compiling
on previous release 4.0b1 but no more with recent.

Wait for Pier to fix it

-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: T. Park [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, April 11, 2001 6:24 PM
>To: [EMAIL PROTECTED]
>Subject: mod_webapp help!
>
>
>
>Hi Folks,
>
>Can anyone advise me how to build it using the sources supplied with
>tomcat 4.0 b3?
>
>My end goal is to be able to build it on NT with MSVC 6.0, but 
>I've been
>trying to get it to
>compile on Solaris 2.8 with the 6.1 C compiler.
>
>I know that it was written for gcc - my next step is to try to 
>use gcc -
>I was hoping to avoid having to employ gcc as it's use will cause me
>some 'productization' headaches)
>
>I'm trying to findout what WA_LOG should be - it's referred to in
>several places but there is not definition of it in the 
>makefiles or the
>C code.
>Also, some of the code constructs appear to be C++ rather than C - was
>this intentional?
>
>e.g.
>    struct wa_connection {....}
>    where wa_connection is subsequently used as a datatype.
>
>In 'strict' C it would be more proper to write something  like:
>
>    typedef struct wa_connection wa_connection_t;
>    struct wa_connection {...}
>
>    and use wa_connection_t as the datatype.
>
>If I feed the former to a 'strict' C compiler - it's not a 
>happy camper.
>
>Note: I'm not trying to be picky here - this just came to light when I
>tried to use Microsoft C and Solaris C on the sources,
>as there were no binaries available for the platforms that I'm using.
>
>I guess my next step is to try with gcc on Solaris and then on windows
>- with some porting work ;-)
>
>Again - is there anyone doing the Win NT work at the moment? If not I'm
>more than happy to volunteer.
>
>-Thom
>
>--
>http://www.borland.com/newsgroups
>http://www.borland.com/devsupport/disclaim.html
>
>

Reply via email to