On Thu, Jul 12, 2001 at 08:55:21AM +0200, [EMAIL PROTECTED] wrote:
> According to ha shao <[EMAIL PROTECTED]>:
> > The latest cvs, clean built, when running, I got:
> > $ ./AbiWord_d
> >
> > **** (1) Assert ****
> > **** (1) m_parserState.m_szSelectedSchemeName at xap_Prefs.cpp:980 ****
> > **** (1) Continue ? (y/n) [y] :
> > Segmentation fault (core dumped)
> >
> > AbiWord_s is the same. Is there any preference I have to set? I didn't
> > see anyone mentioned.
> > It's build without debug.
>
> This is not a bug, it is a feature. You should set ABISUITE_HOME before
> starting AbiWord. Actually "abiword" is a wrapper shell script to do some
> stuff and it is required to use it.
Actually, I also use the abiword script come with debian with the change of
path of the binaries. The same thing happened.
The /usr/share/abisuite is what come with 0.7.14 debian package. Does
the format of abisuite changed lately?
The script I used is attached. Copied from src/pkg/linux/deb/Abiword.
--
Best regard
hashao
#!/bin/sh
# AbiWord wrapper script for Debian GNU/Linux. This script should be
# called "AbiWord" and should reside in /usr/bin.
# debian developer note: staticly linked binaries are heavily discouraged.
# If it were up to me, I'd not even include the lines relating to them.
# Change this if you move the AbiSuite tree.
ABISUITE_HOME=/usr/share/abisuite
export ABISUITE_HOME
# Change this if you move your fonts
ABISUITE_FONT_HOME=$ABISUITE_HOME/fonts
# Hard coded for a Debian system
DYNAMIC_BIN=./AbiWord_d
STATIC_BIN=./AbiWord_s
# Set run-time font path
if [ -d $ABISUITE_FONT_HOME ]
then
xset fp+ $ABISUITE_FONT_HOME 1>/dev/null 2>/dev/null
fi
# Figure out which binary to run
if [ -f $DYNAMIC_BIN ]
then
$DYNAMIC_BIN "$@"
elif [ -f $STATIC_BIN ]
then
$STATIC_BIN "$@"
else
echo "Error: can't find AbiWord executables:"
echo " $DYNAMIC_BIN"
echo " -or-"
echo " $STATIC_BIN"
echo ""
exit
fi
# Set post run-time font path
if [ -d $ABISUITE_FONT_HOME ]
then
xset fp- $ABISUITE_FONT_HOME 1>/dev/null 2>/dev/null
fi
