Hi,
that is the interesting part and could be the reason for the problem.
APserver -d may set --path but only if APSERVER_TRANSPORT != 0
I have added a printout in SVN 401 that prints the APSERVER_TRANSPORT used.
/// Jürgen
On 07/28/2014 04:04 PM, Blake McBride wrote:
It is complaining about --path. I didn't specify --path.
On Mon, Jul 28, 2014 at 8:49 AM, Juergen Sauermann
<[email protected] <mailto:[email protected]>>
wrote:
Hi Blake,
the --port was for older versions of APserver. The absolute latest
should only require -d without --port 16336.
The message you get is still interesting. Can you please check
how APSERVER_TRANSPORT is #defined in config.h?
I would expect this:
#define APSERVER_TRANSPORT 0
#define APSERVER_PORT 16366
/// Jürgen
On 07/28/2014 03:03 PM, Blake McBride wrote:
$ APserver -d --port 16366
cannot specify both --path and --port
On Mon, Jul 28, 2014 at 6:51 AM, Juergen Sauermann
<[email protected]
<mailto:[email protected]>> wrote:
Hi Blake,
interesting. I would propose the following.
1. Start *APserver* manually with *-d* to see some details:
*edjsa@Server65:~/apl/apl-1.3/src$
<mailto:edjsa@Server65:%7E/apl/apl-1.3/src$> APserver -d
--port 16366**
**sizeof(Svar_DB_server) is 32**
**sizeof(Svar_record) is 328**
**sizeof(Svar_partner) is 28**
**APserver: listening on TCP port 16366**
**APserver: entering main loop...**
*
2. In another window, start *apl* with *-l 37*:
*eedjsa@Server65:~/apl/apl-1.3$
<mailto:eedjsa@Server65:%7E/apl/apl-1.3$> apl -l 37**
**sizeof(Svar_record) is 328**
**sizeof(Svar_partner) is 28**
**
**initializing paths from argv[0] = apl**
**initializing paths from $PATH =
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games**
**APL_bin_path is: /usr/local/bin**
**APL_bin_name is: apl**
**Max. Rank is 8**
**sizeof(Value header) is 344 bytes**
**Cell size is 16 bytes**
**Reading config file /usr/local/etc/gnu-apl.d/preferences ...**
**config file /home/eedjsa/.config/gnu-apl/preferences is not
present/readable**
**0 input files:**
**Using TCP socket towards APserver...**
**connected to APserver, socket is 3**
**using Svar_DB on APserver!*
...
The difference between the above output and your output
should tell us what is wrong.
/// Jürgen
On 07/27/2014 08:09 PM, Blake McBride wrote:
I have a shell script that does the build, so ./configure is
always called. Here is the complete output which shows the
version number:
______ _ __ __ __ ___ ____ __
/ ____// | / // / / / / | / __ \ / /
/ / __ / |/ // / / / / /| | / /_/ // /
/ /_/ // /| // /_/ / / ___ | / ____// /___
\____//_/ |_/ \____/ /_/ |_|/_/ /_____/
Welcome to GNU APL version 1.3 / 7691
Copyright (C) 2008-2014 Dr. Jürgen Sauermann
Banner by FIGlet: www.figlet.org <http://www.figlet.org>
This program comes with ABSOLUTELY NO WARRANTY;
for details run: apl --gpl.
This program is free software, and you are welcome to
redistribute it
according to the GNU Public License (GPL) version 3 or later.
⎕SVQ⍳0
Svar_DB not connected in Svar_DB::get_offering_processors()
100 210
On Sun, Jul 27, 2014 at 1:05 PM, Juergen Sauermann
<[email protected]
<mailto:[email protected]>> wrote:
Hi Blake,
not exactly. More like this:
Welcome to GNU APL version 1.3 / 7688
...
⎕SVQ ⍳0
100 210
Looks like some ./configure or installation problem.
Make sure
you did ./configure after last SVN update and see how
(ps -e) APserver
is running.
/// Jürgen
On 07/27/2014 07:54 PM, Blake McBride wrote:
Is this what you intended?
⎕SVQ⍳0
Svar_DB not connected in Svar_DB::get_offering_processors()
100 210
On Sun, Jul 27, 2014 at 12:25 PM, Juergen Sauermann
<[email protected]
<mailto:[email protected]>> wrote:
Hi Blake,
thanks, fixed in SVN 398.
/// Jürgen
On 07/26/2014 12:58 AM, Blake McBride wrote:
⎕SVQ⍳0
Could not open /usr/local/bin/APs : No such file
or directory
Svar_DB not connected in
Svar_DB::get_offering_processors()
100 210
