[omniORB] Error while compiling omniorb

[bjornw@fairplay.no]

"Hasan T. Ozdemir" <htozdemi@top.cis.syr.edu> writes:

> Hi,
> 
> I am getting the following error when I try to compile the source for
> OmniOrb v2.6.1. 
> (I have the source configured for compilation for the following : 
> x86 Redhat linux 5.1,egcs-980302 or later snapshot)
> 
> =========================================================================
>  + /usr/local/egcs/bin/g++ -o omniNames -O2 -Wall -Wno-unused
> -Wl,-rpath,../../../lib/i586_linux_2.0_glibc
> -L../../../lib/i586_linux_2.0_glibc omniNames.o NamingContext_i.o log.o
> -lomniORB2 -lomnithread -lpthread -ltcpwrapGK
> log.o: In function `log::putKey(omniObjectKey const &, ostream &)':
> log.o(.text+0x420c): undefined reference to `operator<<(ostream &,
> smanip<int> const &)'
> log.o(.text+0x4215): undefined reference to `operator<<(ostream &,
> smanip<int> const &)'
> collect2: ld returned 1 exit status
> make[2]: *** [omniNames] Error 1
> make[2]: Leaving directory
> `/usr/local/omniorb/omniORB_2.6.1/src/appl/omniNames'make[1]: *** [export]
> Error 1
> make[1]: Leaving directory `/usr/local/omniorb/omniORB_2.6.1/src/appl'
> make: *** [export] Error 1
> ============================================================================
> 
It seems to me that you have some conflicts between an old gcc installtion
and the new egcs. Try to upgrade to egcs-19981109 and recompile. You must
fix 3-4 errors in some of the headerfiles that defines a variable 'export',
rename it to bexport or something and recompile.

> My setup is the following :
> 
> Redhat Linux 5.1, 
> gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)
> linuxthreads v0.7.1
> 
You need at least glibc-2.0.29 or 2.0.30.
You might want to install binutils-2.9.1.0.15 as well.
If you install RedHat-5.2 you'll get a debugger that supports multi-threading
as well..

> The compilation also gave me a lot of warnings. The warnings were of the
> type "class with private constructor and no friends" and "structure may be
> used before initialized"

Nah - you can just ignore those warnings.