[Fwd: Re: Is building Apache 1.3.20 with Solaris CC 6.0 or 5.0 possible?]

[Justin Erenkrantz <je...@ebuilt.com>]

This is a weird one.  See my reply below for my thoughts.

In short, the answer is no because forte is screaming about the double
declaration of mutex - which seems to be a valid error.  The mutex
in include/multithread.h really needs to be namespace-protected.

Original message here:

http://groups.google.com/groups?hl=en&group=comp.infosystems.www.servers.unix&selm=d1efd44f.0109190840.24ca4739%40posting.google.com

-- justin

--- posting-system@google.com wrote:
> From: posting-system@google.com
> Date: Thu, 20 Sep 2001 00:52:14 -0700
> Reply-to: posting-system@google.com
> To: jerenk@yahoo.com
> Subject: Re: Is building Apache 1.3.20 with Solaris
> CC 6.0 or 5.0 possible?
> 
> From: jerenk@yahoo.com (Justin Erenkrantz)
> Newsgroups: comp.infosystems.www.servers.unix
> Subject: Re: Is building Apache 1.3.20 with Solaris
> CC 6.0 or 5.0 possible?
> References:
> <d1...@posting.google.com>
> NNTP-Posting-Host: 24.13.179.162
> Message-ID:
> <d6...@posting.google.com>
> 
> nick@macaw.demon.co.uk (Nick Lindridge) wrote in
> message
>
news:<d1...@posting.google.com>...
> > Hi,
> > 
> > The answer is of of course yes, but has anyone actually built Apache
> > with Forte or CC 5 recently for Solaris 7 or 8?  Trying regular CC,
> > compat 5 and compat 4 all give up for the same reasons, and I wondered
> > if there are any config options that I've missed to get past the
> > obvious problems. An example build gets a little way and then the
> > output below.
> > 
> > Not sure which is going to be the least pain at this point -
> > installing gcc or fixing up the includes.
> 
> Wow.  It's broken.  I'll take a look at it in a few days. 
> In the meantime, I'd suggest gcc.  sunfreeware.com has 
> pre-built binaries you can download.
> 
> Odd that we haven't caught this before...
> 
> /usr/include/sys/mutex.h is getting included which defines a
> structure called mutex.  I wonder why gcc isn't complaining
> about it.  I wonder if it defines _ASM.  For the complete
> path, sys/mutex.h is included from sys/t_lock.h which is 
> included from sys/file.h which is included from ap_config.h.
> The only way to work around this might be to define _ASM
> before ap_config.h includes sys/file.h.  That's a hack
> though.
> 
> Otherwise, it looks like we may need to go on a type-rename 
> hunt in Apache 1.3.  This won't be fixed until 1.3.21 (at the 
> very least).
> 
> I'm going to CC this to dev@httpd.apache.org.  Feel free to
> keep an eye on the progress there.
> 
> Justin Erenkrantz

----- End forwarded message -----

Re: [Fwd: Re: Is building Apache 1.3.20 with Solaris CC 6.0 or 5.0 possible?]

[Justin Erenkrantz <je...@ebuilt.com>]

On Thu, Sep 20, 2001 at 01:20:05PM -0700, Danek Duvall wrote:
> Do you know why Nick is using the C++ compiler (CC) instead of the C
> compiler (c)?  Apache builds just fine under Solaris 8 and 9 with the Forte
> 6.0 C compiler, but gives the same errors that Nick gets if I use CC
> instead.
> 
> I dunno if that's supposed to work, but he might try g++ and see if that
> gets any further ...

Oh, damn.  I got confused.  You are right - it should be cc not 
CC.  Duh.  It works here.  -- justin

Re: [Fwd: Re: Is building Apache 1.3.20 with Solaris CC 6.0 or 5.0 possible?]

[Danek Duvall <dd...@eng.sun.com>]

Do you know why Nick is using the C++ compiler (CC) instead of the C
compiler (c)?  Apache builds just fine under Solaris 8 and 9 with the Forte
6.0 C compiler, but gives the same errors that Nick gets if I use CC
instead.

I dunno if that's supposed to work, but he might try g++ and see if that
gets any further ...

Danek