From: Andrew Wilson <awilson@hyperreal.com>
Message-Id: <199601022004.MAA23802@taz.hyperreal.com>
Subject: Success compiling for SVR4.2 (UnixWare) (fwd)
To: new-httpd@hyperreal.com
Date: Tue, 2 Jan 1996 12:04:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2166      
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Ack sent.  Does this ring true(er) all you UnixWarers?

Ay.

Forwarded message:
> From squeek!Kazule!crh@kksys.com  Wed Dec 27 15:50:36 1995
> Message-Id: <m0tV5dm-0001vBC@kksys.skypoint.net>
> Date: Wed, 27 Dec 1995 17:45:26 -0600 (CST)
> Reply-To: crh@kazule.ubiqx.mn.org (Christopher R Hertel)
> X-Mailer: ELM [version 2.4 PL17]
> Content-Type: text
> Content-Length: 1547
> From: "Christopher R. Hertel" <crh@Kazule>
> To: squeek!apache.org!apache-bugs
> Subject: Success compiling for SVR4.2 (UnixWare)
> 
> Dear Apache,
> 
> I'm running UnixWare SVR4.2 (1.1.2).  I had to play with things a bit to
> get Apache to compile.  I'm passing the info along, in hopes that it will
> be helpful to someone else. 
> 
> The biggest problem is in the way that UnixWare handles BSD/SVR4 includes,
> libraries, etc.  To work around this problem, I made these definitions in 
> the Configuration file:
> 
> CC= cc
> LFLAGS= -L /usr/ucblib
> EXTRA_LIBS= -ldbm -lucb
> 
> Note that the ndbm library is named libdbm and not libndbm (even though it
> really is ndbm).                      ^^              ^
> 
> The only module that needs these libraries is mod_auth_dbm, which also
> needs the ndbm.h header file located in /usr/ucbinclude.  Unfortunately,
> if I add '-I /usr/ucbinclude' to the CC command line, it messes up the
> compilation of the other files.  So, I patched it by changing the #include
> directive in mod_auth_dbm.c from
> 
>   #include <ndbm.h>
> 
>     to
> 
>   #include "/usr/ucbinclude/ndbm.h"
> 
> There is probably a better way to do this, but it was quick and it worked.
> 
> 
> Note that, under UnixWare, there are *two* possible choices for a C
> compiler included with the stock SDK.
> 
> usr/bin/cc
> usr/ucb/cc
> 
> the latter, in fact, is simply a script that contains the line:
> 
>   /usr/ccs/bin/cc -YP,:/usr/ucblib:/usr/ccs/lib:/usr/lib $@ \
>     -I /usr/ucbinclude -l ucb -l socket -l nsl
> 
> When I attempted to compile using CC= /usr/ucb/cc, I got errors.  The
> problem, again, was adding /usr/ucbinclude to the include path. 
> 
> I hope that this is of use to someone!
> 
> Thanks!
> 
> Chris Hertel
> crh@kazule.ubiqx.mn.org
>