On Thu, 12 Oct 2006, KAYVEN RIESE wrote:
> i'm sorry if i was cranky. i'm going to be more RTFM-y now.
>
> On Wed, 11 Oct 2006, KAYVEN RIESE wrote:
>
>>
>> i finally started rtfm-ing and i am feeling concerned..
>> first of all..
>>
>> /usr/local/mico/BUGS looks alarming
>>
>> be solved in later releases. Please report any new problem with MICO
>> 2.3.9 to mico-devel@mico.org mailing list.
>>
>>
>> single-threaded build bugs
>> --------------------------
>> Following bugs are inherited from standard MICO prior to this release,
>> so they apply to MICO 2.3.8 and older releases too. Anyway
>> single-threaded build of 2.3.9 should be stable as a build of
>> 2.3.8. Any instability should be reported as a regression.
>>
>> - udp transport is not reliable while delivering oneway requests on top
of
>> ST-bu
>> ild
>> - udp transport is broken on FreeBSD 4.7
>> - MICO documentation is out-of-date
>> - compilation of CSL2 fails with gcc3.3/gcc3.4
>> - test case1.idl in test/idl/error fails
>> - compilation of test/idl/25 fails.
>> - IDL compiler doesn't generate error on wrong operation context
>> - IDL compiler handles forward declared interface of already defined
>> interface in wrong way.
>>
>> so now with a ">" for a prompt..
>>
>>> cat /usr/local/mico/VERSION
>> 2.3.12
>>>
>>
>> so i need to deprecate my mico?
>>
>> i moved .. er (cp -r)'ed the /usr/local/mico/demo
>> dingies to ~ but that seemed absurd pathwise but i
>> was like editing all the MakeFiles (why the heck ..
>>
>> is it because of the "BUGS" about documentation?
>>
>>> cat /usr/local/mico/VERSION
>> 2.3.12
>>> pwd
>> /home/kayve/demo
>>> ls
>> MakeVars dispatcher mt
>> MakeVars.install dynany obv
>> MakeVars.install.in externalization pi
>> MakeVars.win32 generic poa
>> Makefile henning random
>> Makefile.win32 interceptor security
>> README interop services
>> bench lifecycle shlib
>> ccm ltp siegel
>> codesets mcast ssl
>> com-interworking mfc
>> csiv2 mico-setup.csh
>>>
>>
>> for example.. okay i can fix this:
>>
>> csiv2 mico-setup.csh
>>> gmake
>> Makefile:23: ../MakeVars: No such file or directory
>> gmake: *** No rule to make target `../MakeVars'. Stop.
>>>
>>
>> by doing a ton of editing.. what the heck?
>>
>> anyway.. i was folling the directions in README
>>
>>
>>> cat README
>>
>> To compile any of the examples you should copy this directory to your
home
>> directory, change into one of the demo directories and type make:
>> cp -r INSTDIR/doc/mico/examples ~/
>> cd ~/examples/account
>> gmake
>> where INSTDIR is the direcory MICO was installed in. If gmake cannot
find
>> mico-c++, mico-ld, or idl you should source the mico-setup script to
setup
>> paths. If your shell is one of csh,tcsh type:
>> source INSTDIR/lib/mico-setup.csh
>> If your shell is one of sh,ash,bash,ksh,zsh type:
>> . INSTDIR/lib/mico-setup.sh
>>
>> Here is a short description of the examples:
>>
>> bench:
>> simple performance measurements. run shellscript 'bench'.
>>
>> shlib:
>> example how to use dynamic object loading. run shellscript
'hello'.
>>
>> services:
>> CORBA services examples.
>>
>> dynany:
>> some examples how to use DynAny.
>>
>> interop:
>> shows MICO's interoperability with other CORBA products.
>>
>> siegel:
>> example from Siegel's CORBA book.
>>
>> henning:
>> patches for the examples form Henning and Vinoski's CORBA book.
>>
>> ssl:
>> SSL example. run shellscript 'ssl'.
>>
>> interceptor:
>> how to use interceptors. run shellscript 'runit'.
>>
>> poa:
>> how to use the Portable Object Adapter (POA)
>>
>> mfc:
>> how to use MICO in conjunction with the Microsoft Foundation Classes
>> (MFC)
>>
>> random:
>> accesses a random number service on the internet (www.random.org)
>>
>> com-interworking:
>> CORBA/COM oneway interworking example
>>
>> codesets:
>> Example showing how to use automatic character set translation
>>
>> mcast:
>> Fault tolerance example using UDP multicasts
>>
>> generic:
>> Demonstrates the implementation of a generic client and server
>> using DII, DSI and DynAny
>>
>>>
>>
>> but there are a lot of problems.. what the heckski? is
>> this the documentation BUG?
>>
>> _______________________________________________
>> 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
>