At 16:33 1/8/2003 +1100, Michael Wardle wrote:
On Wed, 2003-01-08 at 16:25, Lim Kuan Siong wrote:
> Listener.c++:205: `unsetenv' undeclared (first use this function)
IIRC IRIX does not have unsetenv(). Try changing this from
unsetenv(ENVVAR) to setenv(ENVVAR=) or setenv(ENVVAR="").
I used putenv as there is no setenv. It works fine now. However, I'm
encountering an error in Log.c++ now.
The error is:
/usr/freeware/bin/g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include
-DCONFIG_ETC_CONFIG_PATH=\"/usr/local/etc/fam.conf\" -g -O2 -c Log.c++
Log.c++:267: parse error before `char'
Log.c++:271: `file' was not declared in this scope
Log.c++:271: `line' was not declared in this scope
Log.c++:271: `msg' was not declared in this scope
Log.c++:271: ANSI C++ forbids declaration `error' with no type
Log.c++:271: `int Log::error' is not a static member of `class Log'
Log.c++:271: initializer list being treated as compound expression
Log.c++:272: `dirname' was not declared in this scope
Log.c++:272: ANSI C++ forbids declaration `error' with no type
Log.c++:272: `int Log::error' is not a static member of `class Log'
Log.c++:272: initializer list being treated as compound expression
Log.c++:274: parse error before `if'
Log.c++:281: parse error before `if'
Log.c++:284: ANSI C++ forbids declaration `abort' with no type
Log.c++:284: new declaration `int abort()'
/usr/include/stdlib.h:163: ambiguates old declaration `void abort()'
Log.c++:285: parse error before `}'
I have looked at the portion of code & have done the following:
On lines 271 & 272: added (void) in front of Log::error
On line 284: added (void) in front of abort
I presume these were correct & on compilation, the error list got smaller:
/usr/freeware/bin/g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include
-DCONFIG_ETC_CONFIG_PATH=\"/usr/local/etc/fam.conf\" -g -O2 -c Log.c++
Log.c++:267: parse error before `char'
Log.c++:281: parse error before `if'
At this point, I am not able to see any errors in the code to make changes.
Please let me know if I made any errors in my corrections of the code & any
help in figuring this part will be greatly appreciated.
The issues you have raised are exactly the sorts of ones I should test
for with autoconf so the appropriate code can be used on each OS. :-s
I would like to suggest that a web page containing the details of helpful
changes be put up so that it could be referred to when one encounters
errors in the various files. This would greatly aid in troubleshooting any
problems.
Thanks
Thank you very much for your quick response! :)
Regards,
Kuan Siong Lim
Bioinformatics Centre,
National University of Singapore
|