Date: Wed, 09 Dec 1998 17:31:31 -0800 From: Mike Smith <mike@smith.net.au> To: "Russell D. Murphy" <rdmurphy@vt.edu> Cc: FreeBSD-emulation@FreeBSD.ORG Subject: Re: Gauss Message-ID: <199812100131.RAA01775@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 09 Dec 1998 15:19:37 EST." <199812092019.PAA03820@neale.econ.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>
> Has anyone gotten the linux version of gauss (a math and statistics
> package featuring nice matrix processing capabilities, see
> www.aptech.com) to work under stable? I have installed the latest
> linux version of gauss (3.2.43), linux_lib-2.6, and 2.2.8-Stable
> (cvs'd around 1:00pm Nov. 30).
>
> Gauss seems to have an interface program (gauss) which calls another
> program to carry out the actual calculations (gex). Starting gauss
> gives:
>
> ----------
> neale [rdmurphy]% /usr/local/gauss/gauss-3.2.43/gauss -v
> GAUSS Version 3.2.43 (Nov 11 1998)
> (C) Copyright 1984-1998 Aptech Systems, Inc. Maple Valley, WA
> All Rights Reserved.
>
> 10229752 bytes free
>
> (gauss) call ols("",rndu(7,5),rndu(7,1));
> (gauss) x = { 1, 2, 3; 4, 5, 6};
>
> (0) : error G0008 : '' : Syntax error
> (gauss) x = { 1 2 3, 4 5 6 };
> (gauss) quit
> GAUSS terminating...
> neale [rdmurphy]%
> ----------
>
> I've typed four commands at the command prompt; "quit" correctly exits
> and the second matrix assignment (with the ;) correctly indicates a
> syntax error. The other two commands ("call ols" and "x =") generate
> no output, but the following system messages:
>
> ----------
> Dec 9 15:08:02 neale /kernel: pid 3753 (gex), uid 1000: exited on signal 11
> Dec 9 15:10:32 neale /kernel: pid 3769 (gex), uid 1000: exited on signal 11
> ----------
>
> If you've gotten gauss to run, I'd love to hear how you did it. If
> you have any suggestions on what might be wrong, I'd love the hear
> those as well.
The gex program's clearly dying painfully. You should start 'gauss'
under ktrace with:
# ktrace -di gauss
and then feed the ktrace.out file to the linux_kdump utility (you'll
need to install the package). You should be able to find the 'gex'
program dying in there, and the trace of its activity leading up to
that point would be a good place to start.
You might also want to try the patches for -current that we just posted
here since it's quite possible that the pipe bugs will be causing gex
to become confused.
> I've installed linux_devel-0.2 and linux_kdump-1.0, but didn't learn
> too much from trying out linux_kdump (I didn't know much about what to
> look for). If anyone has any pointers, I'm willing to poke around
> some more.
>
>
> Thanks much-
>
> Russ Murphy
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-emulation" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ mike@smith.net.au
\\ The race is long, and in the \\ msmith@freebsd.org
\\ end it's only with yourself. \\ msmith@cdrom.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812100131.RAA01775>