Re: [mico-devel] Problems compiling mico
I have to correct my last post a bit. As I wrote I installed MICO 2.3.13 on Kubuntu 8.10 without problems I did not mention that I had to apply the patch that was posted on this list to avoid the error 'fast_array.cc:51: error: 'UINT_MAX' was not declared in this scope' I had a look about the gcc version on Kubuntu and it states: gcc (Ubuntu 4.3.2-lubuntull) 4.3.2 But the gcc team seems to change some of the headers. I compiled MICO 2.3.13 without any patches and problems on a SUSE 11.1 beta4. The gcc --version output here is: gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291] Andreas ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Problems compiling mico
I had the same issue a few days ago and posted already a patch to this list http://www.mico.org/pipermail/mico-devel/2008-October/010206.html Just include limits.h in the file fast_array.cc In that way it compiles. I did not get already any answer from the developers if this patch is correct, but it seems to work for me. kind regards, Bart Andreas Benzler wrote: I have to correct my last post a bit. As I wrote I installed MICO 2.3.13 on Kubuntu 8.10 without problems I did not mention that I had to apply the patch that was posted on this list to avoid the error 'fast_array.cc:51: error: 'UINT_MAX' was not declared in this scope' I had a look about the gcc version on Kubuntu and it states: gcc (Ubuntu 4.3.2-lubuntull) 4.3.2 But the gcc team seems to change some of the headers. I compiled MICO 2.3.13 without any patches and problems on a SUSE 11.1 beta4. The gcc --version output here is: gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291] Andreas ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Problems compiling mico
Hello Guilherme It might be a gcc 4.3 problem. I have not looked at the code cuasing your problem, code but here http://gcc.gnu.org/gcc-4.3/porting_to.html is this error mentioned because some header includes were removed in the new gcc. There is stated the the header cstring has to be included to solve the problem. By the way, I compiled mico 2.3.13 a couple of days ago myself on a kubuntu 8.10 without any problems, but I hav not checked which gcc version it was exactly. Andreas Benzler In file included from ../include/CORBA.h:280, from ../include/CORBA-SMALL.h:52, from os-unix.cc:34: ../include/mico/throw.h: In function 'void mico_sii_throw(CORBA::StaticRequest*, ...)': ../include/mico/throw.h:111: error: 'strcmp' was not declared in this scope ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
Re: [mico-devel] Problems compiling Mico 2.3.12 with gcc 2.95.4 on Debian Linux
Hi, try to replace ``hh_prefix.clear();'' with ``hh_prefix = ;'' and let me know if it fixes your issue. Cheers, Karel -- Karel Gardas [EMAIL PROTECTED] ObjectSecurity Ltd. http://www.objectsecurity.com --- Need experienced, fast, reliable technical MICO support? --- http://www.objectsecurity.com/mico_commsup_referral.html --- --- On Wed, 27 Sep 2006, John McNamara wrote: Hi, I'm having problems compiling Mico version 2.3.12 on a 2.4.24 Debian Linux system with gcc 2.95.4. I ran configure as follows: ./configure --prefix=/opt/mico --disable-threads The then make which after a while comes up with the following: ... c++ -I. -I../include -O2 -Wall -c params.cc -o params.o params.cc: In method `void IDLParam::set_defaults()': params.cc:84: no matching function for call to `basic_stringchar,string_char_traitschar, __default_alloc_templatetrue,0 ::clear ()' make[1]: *** [params.o] Error 1 make[1]: Leaving directory `/test/mico/idl' make: *** [system] Error 1 My system details are as follows: $ uname -a Linux myhostname 2.4.24 #2 Fri May 7 13:52:02 EEST 2004 i686 unknown $ gcc --version 2.95.4 Mico version 2.3.11 compiles on the same system without any problems. I can compile 2.3.12 with newer compilers/kernels but the target machine, shown above, is outside of my control. Can anyone suggest a workaround for this problem. John. -- ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel ___ Mico-devel mailing list Mico-devel@mico.org http://www.mico.org/mailman/listinfo/mico-devel
