According to [EMAIL PROTECTED]:
> htdig-3.1.1, AIX432, IBM xlC C/C++ compiler v3.6.4:
>
> make[1]: Entering directory `/usr/local/src/htdig-3.1.1/htsearch'
> xlC_r -c -DCONFIG_DIR=\"/usr/local/htdig/conf\"
> -DDEFAULT_CONFIG_FILE=\"/usr/local/htdig/conf/htdig.conf\" -I../htlib
> -I../htcommon -I../db/dist -I../rx/rx -I../include -g -O2 -qmaxmem=8192
> Display.cc
> "../htcommon/DocumentRef.h", line 46.25: 1540-293: (I)
> "DocumentRef::Deserialize(String&)" hides the virtual function
> "Object::Deserialize(String&,int&)".
> "Display.h", line 168.25: 1540-293: (I) "Display::compare(const
> void*,const void*)" hides the virtual function "Object::compare(Object*)".
> "Display.cc", line 1134.25: 1540-016: (S) protected member
> "Display::SortType" cannot be accessed.
> make[1]: *** [Display.o] Error 1
> make[1]: Leaving directory `/usr/local/src/htdig-3.1.1/htsearch'
> make: *** [all] Error 1
>
> Ideas anyone?
D'oh! This problem hasn't shown up with other C++ compilers before, that
I know of. I imagine the problem is that I defined the enum SortType in
the protected section of class Display (in htsearch/Display.h), but it
ought to be moved up to the public section of this class. I had assumed
that because it's only used within the Display class, it can and should
be protected, but just declaring the return type of the sortType() method
in Display.cc requires a reference to this enum from outside of the class,
even though the method itself is a protected member of the class. Bear
with me, I'm just learning C++. Moving up the enum in Display.h would
probably fix the problem. Please let me know ASAP if it does, because
I'd want the fix in the soon-to-be-released 3.1.2.
> Alternative would be a hint how to get gcc/g++ (egcs)
> compiling on AIX432, could not make it work.
Dunno about that. G++ comes prepackaged for my Red Hat Linux system, so
I've never had to build it myself. In any case, we'd like the code to be
portable to most popular C++ compilers, not just GNU's, so we want to fix
the code when we can, rather than having everyone switch to g++/egcs.
As for the two (I) messages above, I assume they are simply informatory,
and not error messages. In C++, it's perfectly normal to have one function
hiding or overriding another function inherited from a parent class.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.