abhishek | 9 Nov 07:24 2009

MICO Compilation using VS .Net 2005

Hi All,

 

I am new to MICO and CORBA. I have a basic question. I hope you will help me.

 

I have downloaded MICO and I was trying to follow README-WIN32 in MICO source.

 

When I built using nmake /f Makefile.win32 everything was OK. I could locate mico\win32-bin directory in MICO source.

I have modified my PATH to include mico\win32-bin.

 

I can not run demos. I am even unable to compile. When I tried to build a project micolib according to the README-WIN32 file, I did not find mico\imr\imr_all.cc in my source tree to include that.

Lots of errors are coming saying cannot include bluetooth.h and so so.

 

I think the README is very old. Can someone please send me the correct settings as the MICO book listed in the site also covers Visual Studio 6 only.

 

Thanks in advance.

 

With Best Regards,

 

Abhishek THAKUR
Systems Engineer
Tel : +91 80 2657 5394 or 5 or 6  Extension 228 Mobile: +91 96117 33117

abhishekh.thakur <at> orange-ftgroup.com

Silicomp India Private Limited
Plot No. 406, 7th Main, First Floor,
Jaya Nagar 2nd Block, Near Vijaya College,
Bangalore – 560 011.

www.itlabs.en.orange-business.com
www.orange-business.com

Please don't print this Email unless you really need to - this will preserve trees on planet earth.

Disclaimer:

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by Silicomp India in this regard and the recipient should carry out such virus and other checks as it considers appropriate”

 

 

 

_______________________________________________
Mico-devel mailing list
Mico-devel <at> mico.org
http://www.mico.org/mailman/listinfo/mico-devel
Eric.Zuur | 9 Nov 10:13 2009
Picon

RE: address.cc assertion failed on x86_64 Ubuntu 9.04

Hi,

I had 64 bit issues with MICO 2.3.11 recently. The program crashed randomly on different points in the code
(mostly CORBA::Buffer).
Our problems seems to be resolved now we have moved to MICO 2.3.13. We are using an older version of GCC
(3.4.x), So your compiler should be better.

You might want to concider moving to MICO 2.3.13 too.

Regards,

Eric.

-----Original Message-----
From: mico-devel-bounces <at> mico.org [mailto:mico-devel-bounces <at> mico.org]On
Behalf Of Jeff Angielski
Sent: Tuesday, October 27, 2009 17:02
To: mico-devel <at> mico.org
Subject: [mico-devel] address.cc assertion failed on x86_64 Ubuntu 9.04

I am not sure my first attempt at sending this was successful so I am 
trying again.  Sorry if it ends up being a double post.

I am unable to compile MICO on a 64bit Ubuntu 9.04 distribution.  The 
idl fails with the following assertion when compiling the first idl file:

$ configure
$ make
   <..snip...>
   /home/jaa/mico/./idl/idl -B../.. --c++-skel --name CosNaming \
                 ../../include/coss/CosNaming.idl
   [1256592588846 - 47360507142816] address.cc:604: assertion failed
   make[2]: *** [CosNaming.cc] Aborted

The assertion is a size mismatch:

     assert (_ipaddr.size() == sizeof (sin.sin_addr.s_addr));

This seems like a fundamental problem with the ORB and 64bit GCC.  Does 
anybody else have this running under this distro?

The gcc that fails is the 4.3.3 gcc on a 64bit machine.

$ gcc --ver
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs 
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr 
--enable-shared --with-system-zlib --libexecdir=/usr/lib 
--without-included-gettext --enable-threads=posix --enable-nls 
--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc 
--enable-mpfr --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)

We have been able to run it with this 4.3.2 gcc on a 32bit machine.

$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
4.3.2-1ubuntu11' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs 
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr 
--enable-shared --with-system-zlib --libexecdir=/usr/lib 
--without-included-gettext --enable-threads=posix --enable-nls 
--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc 
--enable-mpfr --enable-targets=all --enable-checking=release 
--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)

--

-- 
Jeff Angielski
The PTR Group
www.theptrgroup.com
_______________________________________________
Mico-devel mailing list
Mico-devel <at> mico.org
http://www.mico.org/mailman/listinfo/mico-devel
Schlusberg, Arnold R | 16 Nov 21:51 2009

Help - unsatisfied symbols BIO_set_flags and BIO_clear_flags

I have a mico shared library built on an HP Itanium server. When I try
to compile one of my apps, I get the error Unsatisfied symbol
"BIO_set_flags" in /usr/local/lib/libmico2.3.13.sl. Any idea where this
is coming from?

Arnold Schlusberg
FlukeNetworks Inc 
981 Rt 22 W.
Suite 2000
Bridegewater, NJ 08807
Phone: 908-231-9811 ext 107
Fax: 908-231-6833

Please be advised that this email may contain confidential information.
 If you are not the intended recipient, please do not read, copy or
re-transmit this email.  If you have received this email in error,
please notify us by email by replying to the sender and by telephone
(call us collect at +1 202-828-0850) and delete this message and any
attachments.  Thank you in advance for your cooperation and assistance.

In addition, Danaher and its subsidiaries disclaim that the content of
this email constitutes an offer to enter into, or the acceptance of, 
any
contract or agreement or any amendment thereto; provided that the
foregoing disclaimer does not invalidate the binding effect of any
digital or other electronic reproduction of a manual signature that is
included in any attachment to this email.
Karel Gardas | 17 Nov 11:01 2009

Re: Help - unsatisfied symbols BIO_set_flags and BIO_clear_flags

Schlusberg, Arnold R wrote:
> I have a mico shared library built on an HP Itanium server. When I try
> to compile one of my apps, I get the error Unsatisfied symbol
> "BIO_set_flags" in /usr/local/lib/libmico2.3.13.sl. Any idea where this
> is coming from?

That's from one of the OpenSSL libraries.

Cheers,
Karel
--

-- 
Karel Gardas                  kgardas <at> objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com
Karel Gardas | 17 Nov 11:07 2009

Re: address.cc assertion failed on x86_64 Ubuntu 9.04


Jeff,

could you be so kind and test if older version of GNU C++ are able to go
further in compilation? I'm sure MICO is running fine on several
different 64bit OSes while compiled by several different GNU C++
versions. The problem now is that there are few reports on this mailing
list where GNU C++ 4.3.x does not like MICO that much, honestly
speaking. So I would certainly give a try to some of the Ubuntu/Debian
provided older compilers and see if this help or not.

Cheers,
Karel

Jeff Angielski wrote:
> 
> I am not sure my first attempt at sending this was successful so I am
> trying again.  Sorry if it ends up being a double post.
> 
> I am unable to compile MICO on a 64bit Ubuntu 9.04 distribution.  The
> idl fails with the following assertion when compiling the first idl file:
> 
> $ configure
> $ make
>   <..snip...>
>   /home/jaa/mico/./idl/idl -B../.. --c++-skel --name CosNaming \
>                 ../../include/coss/CosNaming.idl
>   [1256592588846 - 47360507142816] address.cc:604: assertion failed
>   make[2]: *** [CosNaming.cc] Aborted
> 
> The assertion is a size mismatch:
> 
>     assert (_ipaddr.size() == sizeof (sin.sin_addr.s_addr));
> 
> 
> This seems like a fundamental problem with the ORB and 64bit GCC.  Does
> anybody else have this running under this distro?
> 
> 
> The gcc that fails is the 4.3.3 gcc on a 64bit machine.
> 
> $ gcc --ver
> Using built-in specs.
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --enable-nls
> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
> --enable-mpfr --with-tune=generic --enable-checking=release
> --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
> 
> 
> We have been able to run it with this 4.3.2 gcc on a 32bit machine.
> 
> $ gcc -v
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.3.2-1ubuntu11' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --enable-nls
> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
> --enable-mpfr --enable-targets=all --enable-checking=release
> --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
> Thread model: posix
> gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)
> 
> 

--

-- 
Karel Gardas                  kgardas <at> objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com
Karel Gardas | 17 Nov 11:11 2009

Re: MICO Compilation using VS .Net 2005


Hi,

first of all make sure you are using at least VC++ 7.1 (VS .Net 2003).
Then download and unpack MICO somewhere, goes to its root directory and
inside the VS command-prompt issue:

nmake /f Makefile.win32

That's all what's needed in order to compile MICO. If you like security
on windows too, then compile OpenSSL somewhere and use
admin\install-openssl.bat <directory> or admin\install-debug-openssl.bat
<directory> in order to copy required libs and header files in the MICO
tree and then issue nmake command above. For running demos you will need
just to add win32-bin into your path.

Cheers,
Karel

abhishek wrote:
> Hi All,
> 
>  
> 
> I am new to MICO and CORBA. I have a basic question. I hope you will help
> me.
> 
>  
> 
> I have downloaded MICO and I was trying to follow README-WIN32 in MICO
> source. 
> 
>  
> 
> When I built using nmake /f Makefile.win32 everything was OK. I could locate
> mico\win32-bin directory in MICO source.
> 
> I have modified my PATH to include mico\win32-bin.
> 
>  
> 
> I can not run demos. I am even unable to compile. When I tried to build a
> project micolib according to the README-WIN32 file, I did not find
> mico\imr\imr_all.cc in my source tree to include that.
> 
> Lots of errors are coming saying cannot include bluetooth.h and so so.
> 
>  
> 
> I think the README is very old. Can someone please send me the correct
> settings as the MICO book listed in the site also covers Visual Studio 6
> only.
> 
>  
> 
> Thanks in advance.
> 
>  
> 
> With Best Regards,
> 
>  
> 
> 
> 
> Abhishek THAKUR
> Systems Engineer
> Tel : +91 80 2657 5394 or 5 or 6  Extension 228 Mobile: +91 96117 33117
> abhishekh.thakur <at> orange-ftgroup.com
> 
> Silicomp India Private Limited
> Plot No. 406, 7th Main, First Floor, 
> Jaya Nagar 2nd Block, Near Vijaya College,
> Bangalore - 560 011. 
> 
>  
> <outbind://10-00000000E63F1A915BD79C4AAA7EE6576E1FFDA524982000/www.itlabs.en
> .orange-business.com> www.itlabs.en.orange-business.com
>  <http://www.orange-business.com/> www.orange-business.com
> 
> 
> 
> Please don't print this Email unless you really need to - this will preserve
> trees on planet earth.
> 
> Disclaimer:
> 
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> Please note that any views or opinions presented in this email are solely
> those of the author and do not necessarily represent those of the company.
> Whilst all reasonable care has been taken to avoid the transmission of
> viruses, it is the responsibility of the recipient to ensure that the onward
> transmission, opening or use of this message and any attachments will not
> adversely affect its systems or data. No responsibility is accepted by
> Silicomp India in this regard and the recipient should carry out such virus
> and other checks as it considers appropriate"
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Mico-devel mailing list
> Mico-devel <at> mico.org
> http://www.mico.org/mailman/listinfo/mico-devel

--

-- 
Karel Gardas                  kgardas <at> objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com
Schlusberg, Arnold R | 17 Nov 17:36 2009

Compiling Error

I am trying to create a mico shared library on an Itanium processor
running HP-UX 11.23. When in the orb/security directory trying to build
the object file for sl3csi_impl.cc I am getting the following two
errors:

"security/sl3csi_impl.cc", line 411: error #2350: more than one operator
"!="
          matches these operands:
            built-in operator "pointer != pointer"
            built-in operator "pointer != pointer"
            operand types are: SL3PM::Principal_var != long
        if (principal_ != NULL) {
                       ^

"security/sl3csi_impl.cc", line 424: error #2350: more than one operator
"!="
          matches these operands:
            built-in operator "pointer != pointer"
            built-in operator "pointer != pointer"
            operand types are: SL3PM::SimplePrincipal_var != long
      if (tprinc != NULL) {

I have built this version of mico on another Itanium earlier this year
with no problems. I don't understand where this error is coming from. I
used the disable-threads and disable-static when I ran configure.

Arnold Schlusberg
FlukeNetworks Inc 
981 Rt 22 W.
Suite 2000
Bridegewater, NJ 08807
Phone: 908-231-9811 ext 107
Fax: 908-231-6833

Please be advised that this email may contain confidential information.
 If you are not the intended recipient, please do not read, copy or
re-transmit this email.  If you have received this email in error,
please notify us by email by replying to the sender and by telephone
(call us collect at +1 202-828-0850) and delete this message and any
attachments.  Thank you in advance for your cooperation and assistance.

In addition, Danaher and its subsidiaries disclaim that the content of
this email constitutes an offer to enter into, or the acceptance of, 
any
contract or agreement or any amendment thereto; provided that the
foregoing disclaimer does not invalidate the binding effect of any
digital or other electronic reproduction of a manual signature that is
included in any attachment to this email.
Diego Sevilla Ruiz | 17 Nov 17:47 2009
Picon

Re: address.cc assertion failed on x86_64 Ubuntu 9.04

Karel,

	Just out of couriosity, does this means that in 64 bit you cannot use 
recent (g++ 4.4) compilers to compile MICO? I've tried myself (with the 
current darcs) and the code compiled, but the tests (the IDL ones) did not 
work (idl/24 failed at least). Would it be hard to fix it?

	Regards,
	diego.

On 17/11/09 11:07, Karel Gardas wrote:
>
> Jeff,
>
> could you be so kind and test if older version of GNU C++ are able to go
> further in compilation? I'm sure MICO is running fine on several
> different 64bit OSes while compiled by several different GNU C++
> versions. The problem now is that there are few reports on this mailing
> list where GNU C++ 4.3.x does not like MICO that much, honestly
> speaking. So I would certainly give a try to some of the Ubuntu/Debian
> provided older compilers and see if this help or not.
>
> Cheers,
> Karel
>
> Jeff Angielski wrote:
>>
>> I am not sure my first attempt at sending this was successful so I am
>> trying again.  Sorry if it ends up being a double post.
>>
>> I am unable to compile MICO on a 64bit Ubuntu 9.04 distribution.  The
>> idl fails with the following assertion when compiling the first idl file:
>>
>> $ configure
>> $ make
>>    <..snip...>
>>    /home/jaa/mico/./idl/idl -B../.. --c++-skel --name CosNaming \
>>                  ../../include/coss/CosNaming.idl
>>    [1256592588846 - 47360507142816] address.cc:604: assertion failed
>>    make[2]: *** [CosNaming.cc] Aborted
>>
>> The assertion is a size mismatch:
>>
>>      assert (_ipaddr.size() == sizeof (sin.sin_addr.s_addr));
>>
>>
>> This seems like a fundamental problem with the ORB and 64bit GCC.  Does
>> anybody else have this running under this distro?
>>
>>
>> The gcc that fails is the 4.3.3 gcc on a 64bit machine.
>>
>> $ gcc --ver
>> Using built-in specs.
>> Target: x86_64-linux-gnu
>> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
>> 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
>> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
>> --enable-shared --with-system-zlib --libexecdir=/usr/lib
>> --without-included-gettext --enable-threads=posix --enable-nls
>> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
>> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
>> --enable-mpfr --with-tune=generic --enable-checking=release
>> --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
>> Thread model: posix
>> gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
>>
>>
>> We have been able to run it with this 4.3.2 gcc on a 32bit machine.
>>
>> $ gcc -v
>> Using built-in specs.
>> Target: i486-linux-gnu
>> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
>> 4.3.2-1ubuntu11' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
>> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
>> --enable-shared --with-system-zlib --libexecdir=/usr/lib
>> --without-included-gettext --enable-threads=posix --enable-nls
>> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
>> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
>> --enable-mpfr --enable-targets=all --enable-checking=release
>> --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
>> Thread model: posix
>> gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)
>>
>>
>
>

--

-- 
Diego Sevilla Ruiz -- http://ditec.um.es/~dsevilla/ -- dsevilla <at> um.es _.___
Dep. Ingeniería y Tecnología de Computadores, Facultad de Informática D|TEC
Univ.de Murcia,Campus Espinardo,30080 Murcia (SPAIN),Tel.+34868887571
Frank Goenninger | 18 Nov 10:35 2009

Compiling Mico on OS X: exception handling mysteries

Hi all:

having configured Mico with

-X-X-X-

PACKAGE=mico
PACKAGE_ROOT_DIR=/opt/orb/$PACKAGE

SRCDIR=/opt/orb/src/$PACKAGE

CONFIGURE_OPTS="--with-tcl=/System/Library/Tcl"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-ccm"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-messaging"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-csl2"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-csiv2"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-sl3"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-naming"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-events"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-streams"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-property"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-trader"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-time"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-life"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-externalize"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-wireless"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-shared"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-dynamic"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-compiled-headers"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-speed-tune"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-except"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-std-eh"
CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-split"
CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-threads"
CONFIGURE_OPTS="$CONFIGURE_OPTS --with-qt=/usr/local/Qt4.5"
CONFIGURE_OPTS="$CONFIGURE_OPTS --prefix=$PACKAGE_ROOT_DIR"

PATH=$PATH:$SRCDIR

PWD=`pwd`
cd $SRCDIR
./configure $CONFIGURE_OPTS
if [ $? -eq 0 ]
then
   make && sudo make install
fi
cd $PWD

-X-X-X-

I get:

g++  -I../include  -O2  -Wall -Wwrite-strings -D_REENTRANT -Wno-long- 
double  -fno-exceptions -DMICO_CONF_NO_EXCEPTIONS  -DPIC  -c dii.cc -o  
dii.pic.o
dii.cc: In member function ‘void CORBA::Request::send_oneway()’:
dii.cc:794: error: exception handling disabled, use -fexceptions to  
enable
make[1]: *** [dii.pic.o] Error 1
make[1]: Leaving directory `/opt/orb/src/mico/orb'
make: *** [system] Error 1

Well, yes, but, ahem, I have told configure to use exception handle,  
or ?

... TIA for any hints ...

Regards,
   Frank
Frank Goenninger | 18 Nov 13:12 2009

Re: Compiling Mico on OS X: exception handling mysteries

... answering this myself:

As soon as you use --enable-speed-tune threading gets disabled.  
Removed the flag and all is ok.

Cheers
    Frank

Am 18.11.2009 um 10:35 schrieb Frank Goenninger:

> Hi all:
>
> having configured Mico with
>
> -X-X-X-
>
> PACKAGE=mico
> PACKAGE_ROOT_DIR=/opt/orb/$PACKAGE
>
> SRCDIR=/opt/orb/src/$PACKAGE
>
> CONFIGURE_OPTS="--with-tcl=/System/Library/Tcl"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-ccm"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-messaging"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-csl2"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-csiv2"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-sl3"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-naming"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-events"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-streams"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-property"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-trader"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-time"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-life"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-externalize"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-wireless"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-shared"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-dynamic"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-compiled-headers"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-speed-tune"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-except"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-std-eh"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --disable-split"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --enable-threads"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --with-qt=/usr/local/Qt4.5"
> CONFIGURE_OPTS="$CONFIGURE_OPTS --prefix=$PACKAGE_ROOT_DIR"
>
> PATH=$PATH:$SRCDIR
>
> PWD=`pwd`
> cd $SRCDIR
> ./configure $CONFIGURE_OPTS
> if [ $? -eq 0 ]
> then
>  make && sudo make install
> fi
> cd $PWD
>
> -X-X-X-
>
> I get:
>
> g++  -I../include  -O2  -Wall -Wwrite-strings -D_REENTRANT -Wno-long- 
> double  -fno-exceptions -DMICO_CONF_NO_EXCEPTIONS  -DPIC  -c dii.cc - 
> o dii.pic.o
> dii.cc: In member function ‘void CORBA::Request::send_oneway()’:
> dii.cc:794: error: exception handling disabled, use -fexceptions to  
> enable
> make[1]: *** [dii.pic.o] Error 1
> make[1]: Leaving directory `/opt/orb/src/mico/orb'
> make: *** [system] Error 1
>
> Well, yes, but, ahem, I have told configure to use exception handle,  
> or ?
>
> ... TIA for any hints ...
>
> Regards,
>  Frank
>
>
> _______________________________________________
> Mico-devel mailing list
> Mico-devel <at> mico.org
> http://www.mico.org/mailman/listinfo/mico-devel

Gmane