David O'Brien writes:
> On Mon, Dec 11, 2000 at 09:07:27AM -0500, Richard J Kuhns wrote:
> > Yes, it's definitely different. No matter what you say when installing,
> > `applix' is:
> >
> > #!/bin/sh
> > APPLIX_HOME="/usr/local/applix"
> > export APPLIX_HOME
> > exec $APPLIX_HOME/applix "$@"
>
> Again lack of details.. :-( EXACTLY what is this file you are showing
> us? Both my of my Applixware 4.42 and 5.0 installations have a real
> binary named `applix' in the root of the install directory. I installed
> 4.42 from the Walnut Creek CDROM CD of it. I installed 5.0 on the first
> tarball package of 5.0 BSDi made (that wasn't released to the public).
> So we also need to know how you got 5.0 (ie, what media are you using).
> Something may have easily changed between what I installed and what BSDi
> is now shipping.
>
OK. In my current installation, it's /usr/local/bin/applix. I installed
from the CD the Walnut Creek/BSDi shipped me (Applixware Office for FreeBSD
v5.0).
I just tried to install it from scratch on a new machine running
4.2-RELEASE.
If I cd to /cdrom/Applix5 and run ./install, I'm not offered a choice
concerning where to install -- it goes under /usr/local.
I just tried `pkg_add -v -p /opt applix-5.0.tgz'. It then put things under
/opt, but /opt/bin/applix was the file I listed above with the hardcoded
"/usr/local/applix". When I changed it to "/opt/applix" and tried to run
it, I got
/usr/libexec/ld-elf.so.1: Shared object "libstdc++.so.2" not found
/prog/applix/axdata/axmain: Operation timed out
Since there's not a libstdc* of any sort under /opt/applix, either
something didn't get installed correctly or applix was compiled using an
older version of the shared library.
At this point, I have some Real Work to do. If there's something else
you'd like me to look at, let me know. It may take me a few hours,
though.
--
Richard Kuhns [EMAIL PROTECTED]
PO Box 6249 Tel: (765)477-6000 \
100 Sawmill Road x319
Lafayette, IN 47903 (800)489-4891 /
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
