Hi Folks,

Has anyone made htdig 3.2.x compile under BSDI 4.01?

Here is my latest unsuccessful stab at compiling 3.20b2 on BSDI with the
following flags and results: 

CFLAGS="-O2"
CXXFLAGS="-O2"
CPPFLAGS="-I/usr/include/g++"
CXX="/usr/bin/g++"
export CFLAGS CXXFLAGS CPPFLAGS CXX
./configure

[...]

gmake
Making all in db
gmake[1]: Entering directory `/tmp/htdig-3.2.0b2/db'
cd dist ; if [ -f Makefile ] ; then gmake PACKAGE=htdig all ; fi
gmake[2]: Entering directory `/tmp/htdig-3.2.0b2/db/dist'
gcc -c -O2 -Wall -I. -I./../include -I/usr/include/g++
-I/usr/include/g++/std -I/usr/local/include -I/usr/local/include
../btree/btc
In file included from /usr/include/g++/std/stddef.h:11,
                 from /usr/include/g++/std/bastring.h:35,
                 from /usr/include/g++/std/string.h:6,
                 from ../btree/bt_compare.c:56:
/usr/include/g++/_G_config.h:39: syntax error before `_G_ptrdiff_t'
/usr/include/g++/_G_config.h:39: warning: data definition has no type or
storage class
/usr/include/g++/_G_config.h:46: syntax error before `_G_wchar_t'
/usr/include/g++/_G_config.h:46: warning: data definition has no type or
storage class
In file included from /usr/include/g++/std/bastring.h:35,
                 from /usr/include/g++/std/string.h:6,
                 from ../btree/bt_compare.c:56:
/usr/include/g++/std/stddef.h:14: syntax error before string constant
/usr/include/g++/std/stddef.h:23: syntax error before `}'
gmake[2]: *** [bt_compare.o] Error 1

As always, any pointers are greatly appreciated.

Regards,

Joe
-- 
     _/   _/_/_/       _/              ____________    __o
     _/   _/   _/      _/         ______________     _-\<,_
 _/  _/   _/_/_/   _/  _/                     ......(_)/ (_)
  _/_/ oe _/   _/.  _/_/ ah        [EMAIL PROTECTED]


------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives:  <http://www.htdig.org/mail/menu.html>
FAQ:            <http://www.htdig.org/FAQ.html>

Reply via email to