Discussion:
Ubuntu build
Andrea Domenici
2009-12-05 09:15:48 UTC
Permalink
Hello!

I have built MICO on a Ubuntu machine. I've had to make two small changes:

1) added
#include <limits.h>
in include/CORBA.h, as UINT_MAX was undefined in orb/fast_array.cc

2) added
#include <mico/ir3.h>
in ccm/mico-ccm.cc as CORBA::ComponentIR was not declared. This
might depend on the fact that at a first attempt I had configured
MICO without --enable-ccm. BTW, it would be nice if this option
were advertised in the INSTALL.txt.

The data about my machine are:

% uname -a
Linux roguestate 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29
UTC 2009 i686 GNU/Linux

% g++ -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--enable-shared --enable-multiarch --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4
--program-suffix=-4.4 --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-objc-gc --enable-targets=all
--disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)

Cheers,

andrea
--
Andrea Domenici

Assistant Professor
Dept. of Information Engineering (DIIEIT), University of Pisa
v. Diotisalvi 2, I-56122 Pisa, Italy
tel: +39 050 2217 674 fax: +39 050 2217600
"Omnia sunt communia" -- Th. Müntzer
Karel Gardas
2009-12-05 12:59:28 UTC
Permalink
Andrea,

could you be so kind and give a try to the latest MICO sources available
in the darcs repository? I hope at least your compilation issues should
be already solved.

Thanks,
Karel
Post by Andrea Domenici
Hello!
1) added
#include <limits.h>
in include/CORBA.h, as UINT_MAX was undefined in orb/fast_array.cc
2) added
#include <mico/ir3.h>
in ccm/mico-ccm.cc as CORBA::ComponentIR was not declared. This
might depend on the fact that at a first attempt I had configured
MICO without --enable-ccm. BTW, it would be nice if this option
were advertised in the INSTALL.txt.
% uname -a
Linux roguestate 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29
UTC 2009 i686 GNU/Linux
% g++ -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--enable-shared --enable-multiarch --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4
--program-suffix=-4.4 --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-objc-gc --enable-targets=all
--disable-werror --with-arch-32=i486 --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)
Cheers,
andrea
--
Karel Gardas ***@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
Andrea Domenici
2009-12-23 14:51:29 UTC
Permalink
Post by Karel Gardas
Andrea,
could you be so kind and give a try to the latest MICO sources available
in the darcs repository? I hope at least your compilation issues should
be already solved.
Hello, Karel!

I have downloaded MICO from the repository this morning, but the
bootstrap.sh script cannot find autoconf 2.13 -- quite obviously, as I
have autoconf 2.64 :

% ./bootstrap.sh
./bootstrap.sh: 21: ERROR: autoconf 2.13 not detected. Tested names are:
autoconf autoconf2.13 autoconf-2.13: not found
% /usr/bin/autoconf --version
autoconf (GNU Autoconf) 2.64


Is there a reason why autoconf 2.13 is needed, and not a later version?
Otherwise, I can change the script so that it ignores the version
number (I am not familiar with bash scripting, so I don't know how to
check that the number is above 2.13).

Cheers,

andrea
--
Andrea Domenici

Assistant Professor
Dept. of Information Engineering (DIIEIT), University of Pisa
v. Diotisalvi 2, I-56122 Pisa, Italy
tel: +39 050 2217 674 fax: +39 050 2217600
"Omnia sunt communia" -- Th. Müntzer
Karel Gardas
2010-01-25 15:49:10 UTC
Permalink
Post by Andrea Domenici
Post by Karel Gardas
Andrea,
could you be so kind and give a try to the latest MICO sources available
in the darcs repository? I hope at least your compilation issues should
be already solved.
Hello, Karel!
I have downloaded MICO from the repository this morning, but the
bootstrap.sh script cannot find autoconf 2.13 -- quite obviously, as I
% ./bootstrap.sh
autoconf autoconf2.13 autoconf-2.13: not found
% /usr/bin/autoconf --version
autoconf (GNU Autoconf) 2.64
Is there a reason why autoconf 2.13 is needed, and not a later version?
Otherwise, I can change the script so that it ignores the version
number (I am not familiar with bash scripting, so I don't know how to
check that the number is above 2.13).
Hello Andrea,

since we're talking about ubuntu here, it shall be straightforward for
you to install autoconf-2.13. IMHO this is the most simple way how to
proceed. IIRC something like `sudo apt-get install autoconf-2.13' shall
work well.
The reason why MICO is still using this old autoconf version is that
during the time it accumulated quite some custom tests (see aclocal.m4)
and I'm not sure they are easily portable to newer autoconf release. The
other reason is that such task is really low-priority since current
autoconf is working well for MICO. Anyway, if you are interested in
newer autoconf support and if you hack something, I would be more than
glad to review your patches and if only a bit possible to merge them to
MICO! As always in free software, volunteers are highly welcome! :-)

Thanks,
Karel
--
Karel Gardas ***@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
Loading...