Subj : Javascript TW2
To   : DIGITAL MAN
From : Dumas Walker
Date : Wed Jan 03 2018 06:51 pm

>> JSexec v3.17a-Linux (rev 1.184)
>> Compiled Nov 4 2017 13:52:09 with GCC 6.3.0
>Okay, that means it hasn't been built since Nov-4-2017, so it won't include the
>fix for JS uifc.

>What's likely happening is that the jsexec you're running is not the latest one
>you built. If you run "locate jsexec" on your system, it should report to all
>of the files named "jsexec" on your file system. My guess is, you have more
>than one.

You are right, but:

/opt/sbbs/exec/jsexec
/opt/sbbs/src/sbbs3/gcc.linux.exe.release/jsexec
/sbbs/exec/jsexec
/sbbs/src/sbbs3/gcc.linux.exe.release/jsexec

Those first two are old, from 2009, and are from a backup of a previous
installation.  The last two are a symlink and an actual build, from
November 4, 2017.  I do not appear to have one more recent.  I have tried
running both "jsexec" and "/sbbs/exec/jsexec" during my attempts.

>When you run jsexec, are you typing the absolute path (e.g. /sbbs/exec/jsexec)
>or just letting your PATH pick the one to run? If you type "which jsexec",
>it'll tell you which one is running (if any) if you just type "jsexec" without
>the path.

I get no output from "which jsexec".

>My guess is that either the jsexec that's in your path is an old one or you're
>specifying the path to /sbbs/exec/jsexec which is an old one. Or maybe it's a
>symlink to src/sbbs3/gcc.linux.exe.debug/jsexec but you built a release binary
>when you ran make (or vice versa).

Apparently I did not build one when I ran make.  :)

>I know this seems like a lot of hassle just to run a door game, but you should
>get a handle on how you can can update sbbs (including jsexec) and actually
>benefit from those updates. :-)

Yes, I would like to get a handle on that, especially since I seem to have
difficulty with it.  Since you did not mention it, I am assuming that I
should be following the directions, as stated, on the UNIX install wiki page
under the "Updating" heading?  That is what I have been trying.

Thanks for you assistance!

on edit:  decided to try something on my own.  I split the line:

cd /sbbs/src/sbbs3; make RELEASE=1 symlinks

into:

cd /sbbs/src/sbbs3
make RELEASE=1 symlinks

Still got the "symlinks" error.  So I ran "make RELEASE=1" in the
/sbbs/src/sbbs3 directory without "symlinks".  Well, that caused *something*
to happen!  It ran 10-15 minutes, compiling this and that, befure ending with
this new error:

make: *** No rule to make target 'base64.h', needed by
'gcc.linux.obj.release-mt/ js_file.o'.  Stop.

If you get this message, I didn't plumb break it.  :D  I also still have a
November 4 version of jsexec, unfortunately.

---
 þ SLMR 2.1a þ He knows changes aren't permanent - but change is!
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * 1-502-875-8938

.