On Dec 7, 2010, at 09:36 , Peter Soetens wrote:

> Most changes were for documentation, but three patches have violated the 'code
> freeze' barrier: the service request disconnection patch and the
> UseOrocos.cmake + ocl updates.
>
> The former would have taken too long until the next major release, and only
> touches a small part of the CORBA transport. The latter was release critical
> for OCL. Markus' getComponentTypes() patch has been applied too.
>
> We're still having issues with the manifest.xml file for ocl:
>
> 'autoproj status':
> manifest /home/kaltan/src/git/orocos-toolchain/ocl/manifest.xml of ocl from
> orocos.toolchain lists 'libreadline' as dependency, but it is neither a normal
> package nor an osdeps package. osdeps reports: there is no osdeps definition
> for libreadline
>
> I could only resolve this by adding to the orocos.osdeps file:
>
> libreadline:
> debian,ubuntu: [libreadline5-dev]
> gentoo: sys-libs/readline
>
> With regard to log4cpp, changing the version numbers turns out to be a hell,
> since the autotools config files in log4cpp are no longer compatible with my
> current installed tools. I get plenty of undefined macros...

Log4cpp needs a major update. I've tried the CMake logic that is now in their SVN repo, but it causes runtime errors in our system. We also get intermittent problems when building using autoconf with the current distro, which is based on a tarball distribution I got from log4cpp many months ago. Overall this needs quite a bit of massaging, and is on my plate for one of my customer's when I get back from holiday in January.

Not sure what I can recommend until then, unless you (or someone else) really wants to get into it.
S