Subj : Javascript TW2
To : Dumas Walker
From : Digital Man
Date : Wed Jan 03 2018 05:30 pm
Re: Javascript TW2
By: Dumas Walker to DIGITAL MAN on Wed Jan 03 2018 06:51 pm
> >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.
Well if you don't have a recent build, then it doesn't really matter which one
you run.
> >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".
Then jsexec is not in your search path (which is fine).
> >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.
Okay, yes, that's correct.
> Thanks for you assistance!
No problem.
> 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.
Then you're missing an update. What was the "cvs update" command you ran when
you updated?
It sounds like you're missing rev 1.42 of src/sbbs3/targets.mk
> 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.
You need to perform a "make clean" first as that file has been moved. See
"Clean Rebuild" at
http://wiki.synchro.net/install:nix#updating
digital man
Synchronet "Real Fact" #68:
Robert D. Bouman, the author of SyncEdit, died in the mid to late 1990's.
Norco, CA WX: 68.3�F, 34.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
