Jon Trulson <jon@radscan.com> writes:
>On Fri, 20 Apr 2001, Nick Ing-Simmons wrote:
>
>> Date: Fri, 20 Apr 2001 12:58:59 +0100 (BST)
>> From: Nick Ing-Simmons <nik@tiuk.ti.com>
>> To: nas@radscan.com
>> Subject: [nas] Solaris, SunRays and NAS
>> 
>> 
>> The option to auto-start a server does not work well on SunRays.
>> It spawns the nasd process fine, but does not pass it a listen argument.
>> So if (as is the case here) the -laudio is trying to connect to 
>> a server from $DISPLAY (say :27.0) then even though the server starts,
>> it is listening on :0 so connect still fails.
>> 
>> Can anyone see why the connection number expected cannot be passed down, 
>> either as command line or by "exporting" DISPLAY/AUDIOSERVER to the nasd
>> process (and have it honour those).
>> 
>
>	None at all... I've attached a patch that should do this
>properly.  It will look for AUDIOSERVER then DISPLAY.  If neither of these
>are set, then :0 is assumed.  Of course specifying the port on the command
>line takes precedence as usual.
>
>	Let me know if it actually works ;-)
The patch had DOS line ends so had to 

perl -pe 's/\r//' 

before patch would take it.

Re-building now.

>
>> Also what is the simplest way to make nas install itself in /usr/local/*
>> rather than what /usr/openwin's configure suggests?
>> 
>
>	Supposedly, something like 'make install DESTDIR=/some/other/dir' 
>will do the trick, though I've never tried this myself.

That _copies_ the files to another location - but does not 
"correct" -DNASCONFSEARCHPATH=\"/etc/nas/\" type things which is 
still going to be looking in where ever openwin's configure has
pointed it. 

>
>> It would also be nice to be able to build nas with gcc rather than 
>> waiting in license queue for a 'cc' license... - but that is another 
>> whole can of worms.
>> 
>
>	Yeah... Isn't that fun :-| Theoretically, you can do this with the
>standard X env (from x.org)  by defining 'HasGcc2' in your systems
>site.def file, and then hoping the proper CFLAGS et. al. are setup in
>sun.cf.
>
>	Of course a better way would be to use autoconf in NAS.  But, that
>too is another can of worms ;-)

Just what does NAS "need to know" in this regard?
It seems it needs to find -lXt and -lX11 and associated socket libraries,
in that sense it is no worse than many other autoconf'ed X applications.
Is there anything deeper?

(My copy of rsynth already has auto-conf probing for various audio 
things, and X libs for linking with -laudio if it can find the latter.)

Another approach that works well for me as a perl expert is to 
re-use perl's Config.pm data which has usually probed for more 
than anything else wants to know.


-- 
Nick Ing-Simmons <nik@tiuk.ti.com>
Via, but not speaking for: Texas Instruments Ltd.


