[nas] Nas-1.5 make error on UnixWare 7

[Jon Trulson]

On Sun, 10 Feb 2002, Matthew Schalit wrote:

> Date: Sun, 10 Feb 2002 02:54:11 -0800
> From: Matthew Schalit <mschalit at pacbell.net>
> To: nas at radscan.com
> Subject: [nas] Nas-1.5 make error on UnixWare 7
> 
> 
> I gave the 1.5 a try and built it exactly like the
> directions mentioned, on UnixWare 7.1.1, using
> 
>   imake -D....
> 
> and it errors out in the lib/audio directory:'
> 
> 
> -----------------------------------------------------
> [snip]
> cc -c -O -Xa -Dasm=__asm -DANSICPP   -I../../include   
> -Dusl -DUSL -DSVR4 -Di386  -DNARROWPROTO -DXTHREADS  
> -D_REENTRANT -DMALLOC_0_RETURNS_NULL -K PIC soundlib.c
> 
> rm -f mutex.o unshared/mutex.o
> 
> cc -c -Xa -Dasm=__asm -DANSICPP  -I../../include -Dusl 
> -DUSL -DSVR4 -Di386  -DNARROWPROTO -DXTHREADS -D_REENTRANT 
> -DMALLOC_0_RETURNS_NULL  -O  mutex.c
> 
> UX:acomp: WARNING: "./mutex.h", line 60: {}-enclosed initializer required
> UX:acomp: WARNING: "./mutex.h", line 60: syntax error:  empty declaration
> UX:acomp: ERROR: "./mutex.h", line 61: internal compiler error:  in_start() with live stack
> make[3]: *** [mutex.o] Error 1
> make[3]: Target `all' not remade because of errors.
> make[3]: Target `all' not remade because of errors.
> make[3]: Leaving directory `/home/matthew/Uber/Dev/nas-1.5/lib/audio'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/matthew/Uber/Dev/nas-1.5/lib'
> [schnip]
> -----------------------------------------------------
> 
> What happened :) ???
> 

	...threadsafety in libaudio ;-)

	Interesting... It does build on UW 2.0.3 (which, admittedly,
is a bit old) with gcc and an X11R6.4 env...

	It looks like XMUTEX_INITIALIZER isn't defined, or is defined
improperly.  On my UW system, XMUTEX_INITIALIZER is defined as '{0}' in
X11/Xthreads.h.  IF you send me your Xthreads.h header file, along with
the output (preprocessor) of:

cc -E -Xa -Dasm=__asm -DANSICPP  -I../../include -Dusl 
 -DUSL -DSVR4 -Di386  -DNARROWPROTO -DXTHREADS -D_REENTRANT
 -DMALLOC_0_RETURNS_NULL  -O  mutex.c

	I could try to take a guess at what it's being set to.

	Also, if you want the thread safe locks to actually do anything,
you need to be sure that XUSE_MTSAFE_API is also defined, otherwise the
lock/unlock calls are noops.  This should be handled in your svr4.cf file
I would think.  

	OR, if you don't really care about threadsafety (ie: no threaded
audio apps), you can just make sure XTHREADS and _REENTRANT are undefined.

-- 
Jon Trulson    mailto:jon at radscan.com
ID: 1A9A2B09, FP: C23F328A721264E7 B6188192EC733962
PGP keys at http://radscan.com/~jon/PGPKeys.txt
#include <std/disclaimer.h>
Bad Color Temperature, Too much Peach.