I believe the intent was that you remove the .h from the C++
standard library includes. It sounds like you removed the .h from
all of the includes. If you are going to try modifying the
include statements in this file, you should limit your changes to
ostream.h and iostream.h. However you may run into additional
scoping problems if you remove the .h's, depending on whether the
std namespace is visible.

Did you try the patch that Geoff suggested? Or did you just hack
the configuration test directly? You only stated that you changed
fstream.h to fstream in the configuration files. This alone is
not likely to address all of the problems introduced by GCC's
warning messages. In particular, ostream.h and iostream.h will
still be interpreted as missing, and the HAVE_OSTREAM_H and
HAVE_IOSTREAM_H ifdef's will prevent either header from being
included.

Jim

Sixbury, Dan's bits of Wed, 25 Sep 2002 translated to:

>Geoff,
>
>I updated the htString.h file in /opt/htdig-3.1.6/htlib to remove the .h
>from the #include lines.  I reran the make and ended up with the following
>errors.
>
>Thanks,
>Dan
>
># make
>make[1]: Entering directory `/opt/htdig-3.1.6/db/dist'
>/usr/bin/rm -f libdb.a
>/usr/ccs/bin/ar cr libdb.a bt_compare.o bt_conv.o bt_curadj.o bt_cursor.o
>bt_delete.o bt_open.o bt_page.o bt_put.o bt_rec.o bt_recno.o bt_rsearch.o
>bt_search.o bt_split.o bt_stat.o btree_auto.o db.o db_appinit.o db_am.o
>db_apprec.o db_auto.o db_byteorder.o db_conv.o db_dispatch.o db_dup.o
>db_err.o db_iface.o db_join.o db_log2.o db_overflow.o db_pr.o db_rec.o
>db_region.o db_ret.o db_salloc.o db_shash.o dbm.o hash.o hash_auto.o
>hash_conv.o hash_dup.o hash_func.o hash_page.o hash_rec.o hash_stat.o
>hsearch.o lock.o lock_conflict.o lock_deadlock.o lock_util.o lock_region.o
>log.o log_archive.o log_auto.o log_compare.o log_findckp.o log_get.o
>log_put.o log_rec.o log_register.o mp_bh.o mp_fget.o mp_fopen.o mp_fput.o
>mp_fset.o mp_open.o mp_pr.o mp_region.o mp_sync.o mutex.o os_abs.o
>os_alloc.o os_config.o os_dir.o os_fid.o os_fsync.o os_map.o os_oflags.o
>os_open.o os_rpath.o os_rw.o os_seek.o os_sleep.o os_spin.o os_stat.o
>os_tmpdir.o os_unlink.o txn.o txn_auto.o txn_rec.o xa.o xa_db.o xa_map.o
>strsep.o
>test ! -f /usr/ccs/bin/ranlib || /usr/ccs/bin/ranlib libdb.a
>gcc -o db_archive  db_archive.o err.o getlong.o libdb.a -lthread
>gcc -o db_checkpoint  db_checkpoint.o err.o getlong.o libdb.a -lthread
>gcc -o db_deadlock  db_deadlock.o err.o getlong.o libdb.a -lthread
>gcc -o db_dump  db_dump.o err.o getlong.o libdb.a -lthread
>gcc -o db_load  db_load.o err.o getlong.o libdb.a -lthread
>gcc -o db_printlog  db_printlog.o err.o getlong.o libdb.a -lthread
>gcc -o db_recover  db_recover.o err.o getlong.o libdb.a -lthread
>gcc -o db_stat  db_stat.o err.o getlong.o libdb.a -lthread
>make[1]: Leaving directory `/opt/htdig-3.1.6/db/dist'
>make[1]: Entering directory `/opt/htdig-3.1.6/htlib'
>c++ -c  -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib
>-I../htcommon -I../db/dist -I../include -g -O2 Configuration.cc
>In file included from Configuration.cc:13:
>htString.h:15:18: Object: No such file or directory
>htString.h:16:18: stdarg: No such file or directory
>htString.h:17:17: stdio: No such file or directory
>In file included from Configuration.cc:13:
>htString.h:139: `ostream' was not declared in this scope
>htString.h:139: `o' was not declared in this scope
>htString.h:139: invalid data member initialization
>htString.h:139: (use `=' to initialize static data members)
>htString.h:139: variable or field `debug' declared void
>htString.h:152: ISO C++ forbids declaration of `ostream' with no type
>htString.h:152: `ostream' is neither function nor member function; cannot be
>   declared friend



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to