Hi,

I have been encountering the following error when running ./configure && make for 
aspell-0.50.3:

Making all in auto
make[1]: Entering directory `/home/mark/Source/aspell-0.50.3/auto'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mark/Source/aspell-0.50.3/auto'
Making all in common
make[1]: Entering directory `/home/mark/Source/aspell-0.50.3/common'
make  all-am
make[2]: Entering directory `/home/mark/Source/aspell-0.50.3/common'
if /bin/sh ../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.     -g -O2 -MT 
posib_err.lo -MD -MP -MF ".deps/posib_err.Tpo" \
  -c -o posib_err.lo `test -f 'posib_err.cpp' || echo './'`posib_err.cpp; \
then mv ".deps/posib_err.Tpo" ".deps/posib_err.Plo"; \
else rm -f ".deps/posib_err.Tpo"; exit 1; \
fi
 g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT posib_err.lo -MD -MP -MF 
.deps/posib_err.Tpo -c posib_err.cpp  -fPIC -DPIC
posib_err.cpp: In member function `acommon::PosibErrBase&
   acommon::PosibErrBase::with_file(acommon::ParmString)':
posib_err.cpp:77: error: non-lvalue in unary `&'
make[2]: *** [posib_err.lo] Error 1
make[2]: Leaving directory `/home/mark/Source/aspell-0.50.3/common'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/mark/Source/aspell-0.50.3/common'
make: *** [all-recursive] Error 1
[EMAIL PROTECTED]:~/Source/aspell-0.50.3>

Configure runs fine with no obvious errors that I can see.  I have run a search on the 
archives as well as google and came up with one reference to a problem of a missing 
libstdc++-devel.  I have this installed on my machine.

I am running SuSE 8.2 Pro with a stock kernel and gcc 3.3-23 and glibc 2.3.2-6.

Does anyone know what I need to do to fix this?

TIA
-- 
Mark        Registered Linux User #219700     http://counter.li.org

"The kind of person who always insists on his way of seeing things
  can never learn anything from anyone."  Lao Tzu, Tao Te Ching


_______________________________________________
Aspell-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/aspell-user

Reply via email to