Mico CORBA is a CORBA implementation, used among others in OpenModelica (which I am trying to get into portage...). Mico has been certified "CORBA compliant" since 1999, and is programmed in C++; see http://www.mico.org. I would expect it to end up in the net-misc category.
Created attachment 158161 [details] Ebuild for Mico CORBA The ebuild has been tested successfully on a amd64 machine.
(In reply to comment #1) > Created an attachment (id=158161) [edit] > Ebuild for Mico CORBA > > The ebuild has been tested successfully on a amd64 machine. Then it should be: -KEYWORDS="~amd64 ~x86" +KEYWORDS="~amd64"
Created attachment 158185 [details] Updated ebuild Hi Jeroen, you're right of course. I have the habit of adding ~x86 automatically since when I had a Gentoo x86 machine at work I would use to test ebuilds, but I switched job twice in the meantime... old habits are hard to break. I also changed the LICENSE variable, since I have seen that other packages with similar license conditions write "LGPL-2 GPL-2" (eg. omniORB).
Created attachment 158807 [details] Updated ebuild, quotes Add quotes around variables to ensure correct expansion.
Hello, there is an ebuild for mico-2.3.12 out there on the sunrise overlay: http://overlays.gentoo.org/proj/sunrise/browser/reviewed/net-misc/mico/mico-2.3.12.ebuild which is based on bug 122141. Therefore, I think, this bug should be closed.
tested on a x86 machine with GCC 4.3.1 and doesn't compile (error in orb_all.pic.o)
(In reply to comment #6) > tested on a x86 machine with GCC 4.3.1 and doesn't compile (error in > orb_all.pic.o) > also the new mico-2.3.13 doesn't compile.
(In reply to comment #7) > (In reply to comment #6) > > tested on a x86 machine with GCC 4.3.1 and doesn't compile (error in > > orb_all.pic.o) > > also the new mico-2.3.13 doesn't compile. Don't have gcc-4.2 or 4.3 here yet, but does it help to avoid '--enable-final' ? AFAICS, compiling with more than one job becomes possible then.
I'm going to maintain mico and am likely to put in 2.3.13 soon. *** This bug has been marked as a duplicate of bug 257984 ***