orocos build fail on debian wheezy

Hello,

I'm installing orocos on debian wheezy ( following the instructions at
http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux )

The output of command: ruby --version is
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]

after typing: sh bootstrap.sh, the build fails at some point and tells
to look at utilrb-post-install.log for details. A relevant looking
snippet from that file is

------
2012-10-06 22:34:52 +0200: running
rake default
in directory /home/sagar/oroom/orocos-toolchain/utilrb
INFO: cannot load the Hoe gem. Distribution is disabled
INFO: error message is: cannot load such file -- hoe
creating Makefile
linking shared-object utilrb_ext.so
g++: error: unrecognized command line option ‘-module’
make: *** [utilrb_ext.so] Error 1
rake aborted!
cannot build the C extension
------

Any ideas what is wrong and how to fix it?

Thanks in advance,
Sagar

orocos build fail on debian wheezy

On 10/06/2012 10:43 PM, Sagar Behere wrote:
> Hello,
>
> I'm installing orocos on debian wheezy ( following the instructions at
> http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux )
>
> The output of command: ruby --version is
> ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
>
> after typing: sh bootstrap.sh, the build fails at some point and tells
> to look at utilrb-post-install.log for details. A relevant looking
> snippet from that file is
>
> ------
> 2012-10-06 22:34:52 +0200: running
> rake default
> in directory /home/sagar/oroom/orocos-toolchain/utilrb
> INFO: cannot load the Hoe gem. Distribution is disabled
> INFO: error message is: cannot load such file -- hoe
> creating Makefile
> linking shared-object utilrb_ext.so
> g++: error: unrecognized command line option ‘-module’
> make: *** [utilrb_ext.so] Error 1
> rake aborted!
> cannot build the C extension
> ------
>
> Any ideas what is wrong and how to fix it?

Okay, I found some fixes that work for the above and subsequent
problems. These fixes seem to make it compile, but I don't really know
what they do (they are a result of long trial and error) so maybe the
developers should take a look.

It may be that some of the problems occur because Debian Wheezy uses g++
version 4.7.1

Anyhoo, here are the fixes.
------------------
For making utilrb build:

gem install hoe

edit the utilrb/ext/extconf.rb file and comment out the line

$LDFLAGS += " -module"

Once this is done, the build can be continued with

autoproj rebuild

but it soon fails while compiling typelib, with relevant errors

--------
[ 61%] Building CXX object
bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE, VALUE, VALUE)’:
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:290:40:
error: format not a string literal and no format arguments
[-Werror=format-security]
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
function ‘VALUE value_initialize(VALUE, VALUE)’:
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:345:46:
error: format not a string literal and no format arguments
[-Werror=format-security]
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:512:40:
error: format not a string literal and no format arguments
[-Werror=format-security]
cc1plus: some warnings being treated as errors
make[2]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o] Error 1
make[1]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/all] Error 2
make: *** [all] Error 2
--------

It seems that in Debian Wheezy, ruby1.9 uses -Werror=format-security
instead of -Wformat-security. The fix for this is to edit the
typelib/bindings/ruby/ext/value.cc file as follows:

modify all occurrences of
rb_raise(rb_eArgError, e.what());
(which occur on lines 290, 345, 512) as
rb_raise(rb_eArgError, "%s", e.what());

The same applies to typelib/bindings/ruby/ext/specialized_types.cc on
lines 54 and 69 and
/home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/registry.cc
on lines 166 and 277

After this, autoproj build is successful.

Hope this helps,
Sagar

orocos build fail on debian wheezy

Hi Sagar,

There were earlier reports about wheezy. Sylvain has fixed them on the rock
branches and they are being prepared to merge on master.

So if you would check the master branches, i believe most issues will be
fixed already.

Peter

Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...) het
volgende:

> On 10/06/2012 10:43 PM, Sagar Behere wrote:
> > Hello,
> >
> > I'm installing orocos on debian wheezy ( following the instructions at
> > http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux )
> >
> > The output of command: ruby --version is
> > ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> >
> > after typing: sh bootstrap.sh, the build fails at some point and tells
> > to look at utilrb-post-install.log for details. A relevant looking
> > snippet from that file is
> >
> > ------
> > 2012-10-06 22:34:52 +0200: running
> > rake default
> > in directory /home/sagar/oroom/orocos-toolchain/utilrb
> > INFO: cannot load the Hoe gem. Distribution is disabled
> > INFO: error message is: cannot load such file -- hoe
> > creating Makefile
> > linking shared-object utilrb_ext.so
> > g++: error: unrecognized command line option ‘-module’
> > make: *** [utilrb_ext.so] Error 1
> > rake aborted!
> > cannot build the C extension
> > ------
> >
> > Any ideas what is wrong and how to fix it?
>
> Okay, I found some fixes that work for the above and subsequent
> problems. These fixes seem to make it compile, but I don't really know
> what they do (they are a result of long trial and error) so maybe the
> developers should take a look.
>
> It may be that some of the problems occur because Debian Wheezy uses g++
> version 4.7.1
>
> Anyhoo, here are the fixes.
> ------------------
> For making utilrb build:
>
> gem install hoe
>
> edit the utilrb/ext/extconf.rb file and comment out the line
>
> $LDFLAGS += " -module"
>
> Once this is done, the build can be continued with
>
> autoproj rebuild
>
> but it soon fails while compiling typelib, with relevant errors
>
> --------
> [ 61%] Building CXX object
> bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE, VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:290:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE value_initialize(VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:345:46:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:512:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> cc1plus: some warnings being treated as errors
> make[2]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o] Error
> 1
> make[1]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/all] Error 2
> make: *** [all] Error 2
> --------
>
> It seems that in Debian Wheezy, ruby1.9 uses -Werror=format-security
> instead of -Wformat-security. The fix for this is to edit the
> typelib/bindings/ruby/ext/value.cc file as follows:
>
> modify all occurrences of
> rb_raise(rb_eArgError, e.what());
> (which occur on lines 290, 345, 512) as
> rb_raise(rb_eArgError, "%s", e.what());
>
> The same applies to typelib/bindings/ruby/ext/specialized_types.cc on
> lines 54 and 69 and
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/registry.cc
> on lines 166 and 277
>
> After this, autoproj build is successful.
>
>
> Hope this helps,
> Sagar
> --
> Orocos-Users mailing list
> Orocos-Users [..] ... <javascript:;>
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

orocos build fail on debian wheezy

On 10/07/2012 10:24 PM, Peter Soetens wrote:
> Hi Sagar,
>
> There were earlier reports about wheezy. Sylvain has fixed them on the
> rock branches and they are being prepared to merge on master.

Oh, okay.

> So if you would check the master branches, i believe most issues will be
> fixed already.

When I do 'sh bootstrap.sh' as part of the recommended install
procedure, does it pull from the master branches on gitorious? If yes,
then the issues weren't fixed as of today afternoon, which is when I
faced the issues. If no, could you tell me how to check the master branches?

Thanks and regards,
Sagar

> Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...
> <mailto:sagar [dot] behere [..] ...>) het volgende:
>
> On 10/06/2012 10:43 PM, Sagar Behere wrote:
> > Hello,
> >
> > I'm installing orocos on debian wheezy ( following the
> instructions at
> > http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux )
> >
> > The output of command: ruby --version is
> > ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> >
> > after typing: sh bootstrap.sh, the build fails at some point and
> tells
> > to look at utilrb-post-install.log for details. A relevant looking
> > snippet from that file is
> >
> > ------
> > 2012-10-06 22:34:52 +0200: running
> > rake default
> > in directory /home/sagar/oroom/orocos-toolchain/utilrb
> > INFO: cannot load the Hoe gem. Distribution is disabled
> > INFO: error message is: cannot load such file -- hoe
> > creating Makefile
> > linking shared-object utilrb_ext.so
> > g++: error: unrecognized command line option ‘-module’
> > make: *** [utilrb_ext.so] Error 1
> > rake aborted!
> > cannot build the C extension
> > ------
> >
> > Any ideas what is wrong and how to fix it?
>
> Okay, I found some fixes that work for the above and subsequent
> problems. These fixes seem to make it compile, but I don't really know
> what they do (they are a result of long trial and error) so maybe the
> developers should take a look.
>
> It may be that some of the problems occur because Debian Wheezy uses g++
> version 4.7.1
>
> Anyhoo, here are the fixes.
> ------------------
> For making utilrb build:
>
> gem install hoe
>
> edit the utilrb/ext/extconf.rb file and comment out the line
>
> $LDFLAGS += " -module"
>
> Once this is done, the build can be continued with
>
> autoproj rebuild
>
> but it soon fails while compiling typelib, with relevant errors
>
> --------
> [ 61%] Building CXX object
> bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE, VALUE, VALUE)’:
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:290:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE value_initialize(VALUE, VALUE)’:
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:345:46:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc: In
> function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/value.cc:512:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> cc1plus: some warnings being treated as errors
> make[2]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/ext/value.o]
> Error 1
> make[1]: *** [bindings/ruby/CMakeFiles/typelib_ruby.dir/all] Error 2
> make: *** [all] Error 2
> --------
>
> It seems that in Debian Wheezy, ruby1.9 uses -Werror=format-security
> instead of -Wformat-security. The fix for this is to edit the
> typelib/bindings/ruby/ext/value.cc file as follows:
>
> modify all occurrences of
> rb_raise(rb_eArgError, e.what());
> (which occur on lines 290, 345, 512) as
> rb_raise(rb_eArgError, "%s", e.what());
>
> The same applies to typelib/bindings/ruby/ext/specialized_types.cc on
> lines 54 and 69 and
> /home/sagar/oroom/orocos-autoproj/typelib/bindings/ruby/ext/registry.cc
> on lines 166 and 277
>
> After this, autoproj build is successful.
>
>
> Hope this helps,
> Sagar
> --
> Orocos-Users mailing list
> Orocos-Users [..] ... <javascript:;>
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>

orocos build fail on debian wheezy

Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...) het
volgende:

> On 10/07/2012 10:24 PM, Peter Soetens wrote:
>
>> Hi Sagar,
>>
>> There were earlier reports about wheezy. Sylvain has fixed them on the
>> rock branches and they are being prepared to merge on master.
>>
>
> Oh, okay.
>
> So if you would check the master branches, i believe most issues will be
>> fixed already.
>>
>
> When I do 'sh bootstrap.sh' as part of the recommended install procedure,
> does it pull from the master branches on gitorious? If yes, then the issues
> weren't fixed as of today afternoon, which is when I faced the issues. If
> no, could you tell me how to check the master branches?

Check the contents of bootstrap.sh, its quite trivial. Just change the
toolchain-2.5 argument to master.

Peter

>
> Thanks and regards,
> Sagar
>
> Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...
>> <mailto:sagar [dot] behere [..] ...>) het volgende:
>>
>> On 10/06/2012 10:43 PM, Sagar Behere wrote:
>> > Hello,
>> >
>> > I'm installing orocos on debian wheezy ( following the
>> instructions at
>> > http://www.orocos.org/wiki/**orocos/toolchain/quick-start-**linux<http:/...)
>> >
>> > The output of command: ruby --version is
>> > ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
>> >
>> > after typing: sh bootstrap.sh, the build fails at some point and
>> tells
>> > to look at utilrb-post-install.log for details. A relevant looking
>> > snippet from that file is
>> >
>> > ------
>> > 2012-10-06 22:34:52 +0200: running
>> > rake default
>> > in directory /home/sagar/oroom/orocos-**toolchain/utilrb
>> > INFO: cannot load the Hoe gem. Distribution is disabled
>> > INFO: error message is: cannot load such file -- hoe
>> > creating Makefile
>> > linking shared-object utilrb_ext.so
>> > g++: error: unrecognized command line option ‘-module’
>> > make: *** [utilrb_ext.so] Error 1
>> > rake aborted!
>> > cannot build the C extension
>> > ------
>> >
>> > Any ideas what is wrong and how to fix it?
>>
>> Okay, I found some fixes that work for the above and subsequent
>> problems. These fixes seem to make it compile, but I don't really know
>> what they do (they are a result of long trial and error) so maybe the
>> developers should take a look.
>>
>> It may be that some of the problems occur because Debian Wheezy uses
>> g++
>> version 4.7.1
>>
>> Anyhoo, here are the fixes.
>> ------------------
>> For making utilrb build:
>>
>> gem install hoe
>>
>> edit the utilrb/ext/extconf.rb file and comment out the line
>>
>> $LDFLAGS += " -module"
>>
>> Once this is done, the build can be continued with
>>
>> autoproj rebuild
>>
>> but it soon fails while compiling typelib, with relevant errors
>>
>> --------
>> [ 61%] Building CXX object
>> bindings/ruby/CMakeFiles/**typelib_ruby.dir/ext/value.o
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**ruby/ext/value.cc:
>> In
>> function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE, VALUE,
>> VALUE)’:
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**
>> ruby/ext/value.cc:290:40:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**ruby/ext/value.cc:
>> In
>> function ‘VALUE value_initialize(VALUE, VALUE)’:
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**
>> ruby/ext/value.cc:345:46:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**ruby/ext/value.cc:
>> In
>> function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**
>> ruby/ext/value.cc:512:40:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>> cc1plus: some warnings being treated as errors
>> make[2]: *** [bindings/ruby/CMakeFiles/**
>> typelib_ruby.dir/ext/value.o]
>> Error 1
>> make[1]: *** [bindings/ruby/CMakeFiles/**typelib_ruby.dir/all] Error
>> 2
>> make: *** [all] Error 2
>> --------
>>
>> It seems that in Debian Wheezy, ruby1.9 uses -Werror=format-security
>> instead of -Wformat-security. The fix for this is to edit the
>> typelib/bindings/ruby/ext/**value.cc file as follows:
>>
>> modify all occurrences of
>> rb_raise(rb_eArgError, e.what());
>> (which occur on lines 290, 345, 512) as
>> rb_raise(rb_eArgError, "%s", e.what());
>>
>> The same applies to typelib/bindings/ruby/ext/**specialized_types.cc
>> on
>> lines 54 and 69 and
>> /home/sagar/oroom/orocos-**autoproj/typelib/bindings/**
>> ruby/ext/registry.cc
>> on lines 166 and 277
>>
>> After this, autoproj build is successful.
>>
>>
>> Hope this helps,
>> Sagar
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ... <javascript:;>
>> http://lists.mech.kuleuven.be/**mailman/listinfo/orocos-users<http://lis...
>>
>>
>

orocos build fail on debian wheezy

On 10/07/2012 10:44 PM, Peter Soetens wrote:
>
>
> Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...
> <mailto:sagar [dot] behere [..] ...>) het volgende:
>
> On 10/07/2012 10:24 PM, Peter Soetens wrote:
>
> Hi Sagar,
>
> There were earlier reports about wheezy. Sylvain has fixed them
> on the
> rock branches and they are being prepared to merge on master.
>
>
> Oh, okay.
>
> So if you would check the master branches, i believe most issues
> will be
> fixed already.
>
>
> When I do 'sh bootstrap.sh' as part of the recommended install
> procedure, does it pull from the master branches on gitorious? If
> yes, then the issues weren't fixed as of today afternoon, which is
> when I faced the issues. If no, could you tell me how to check the
> master branches?
>
>
> Check the contents of bootstrap.sh, its quite trivial. Just change the
> toolchain-2.5 argument to master.

When I switch to branch master and run the installation, it stops at
some point with the message

---
manifest /home/sagar/excludes/orocos-toolchain/ocl/manifest.xml of ocl
from orocos.toolchain lists 'libncurses-dev' as dependency, but it is
neither a normal package nor an osdeps package. osdeps reports: there is
no osdeps definition for libncurses-dev
---

libncurses-dev and libncurses5-dev are installed on the system.
Modifying the ocl/manifest.xml file to make it libncurses5-dev, makes no
difference. That error still appears, but for libncurses5-dev.

For now, I simply removed the line from the manifest.xml, because I know
the package is installed and so hopefully the ocl will still compile.

However, the compile halts later with

------
[ 94%] Building CXX object lua/CMakeFiles/rttlua-tlsf.dir/rtt.cpp.o
Linking CXX executable ../../bin/rttlua-corba-gnulinux
CMakeFiles/rttlua-corba.dir/LuaComponent.cpp.o: In function
`ORO_main_impl(int, char**)':
/home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:301:
undefined reference to
`OCL::logging::Category::createOCLCategory(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&,
log4cpp::Category*, int)'
/home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:301:
undefined reference to
`log4cpp::HierarchyMaintainer::set_category_factory(log4cpp::Category*
(*)(std::basic_string<char, std::char_traits<char>, std::allocator<char>
> const&, log4cpp::Category*, int))'
/home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:371:
undefined reference to
`log4cpp::HierarchyMaintainer::getDefaultMaintainer()'
/home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:372:
undefined reference to
`log4cpp::HierarchyMaintainer::getDefaultMaintainer()'
collect2: ld returned 1 exit status
------

This error isn't present in the toolchain-2.5 branch.

Regards,
Sagar

> Peter
>
>
> Thanks and regards,
> Sagar
>
> Op zondag 7 oktober 2012 schreef Sagar Behere
> (sagar [dot] behere [..] ...
> <mailto:sagar [dot] behere [..] ...>) het volgende:
>
> On 10/06/2012 10:43 PM, Sagar Behere wrote:
> > Hello,
> >
> > I'm installing orocos on debian wheezy ( following the
> instructions at
> >
> http://www.orocos.org/wiki/__orocos/toolchain/quick-start-__linux <http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux>
> )
> >
> > The output of command: ruby --version is
> > ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> >
> > after typing: sh bootstrap.sh, the build fails at some point and
> tells
> > to look at utilrb-post-install.log for details. A relevant
> looking
> > snippet from that file is
> >
> > ------
> > 2012-10-06 22:34:52 +0200: running
> > rake default
> > in directory /home/sagar/oroom/orocos-__toolchain/utilrb
> > INFO: cannot load the Hoe gem. Distribution is disabled
> > INFO: error message is: cannot load such file -- hoe
> > creating Makefile
> > linking shared-object utilrb_ext.so
> > g++: error: unrecognized command line option ‘-module’
> > make: *** [utilrb_ext.so] Error 1
> > rake aborted!
> > cannot build the C extension
> > ------
> >
> > Any ideas what is wrong and how to fix it?
>
> Okay, I found some fixes that work for the above and subsequent
> problems. These fixes seem to make it compile, but I don't
> really know
> what they do (they are a result of long trial and error) so
> maybe the
> developers should take a look.
>
> It may be that some of the problems occur because Debian
> Wheezy uses g++
> version 4.7.1
>
> Anyhoo, here are the fixes.
> ------------------
> For making utilrb build:
>
> gem install hoe
>
> edit the utilrb/ext/extconf.rb file and comment out the line
>
> $LDFLAGS += " -module"
>
> Once this is done, the build can be continued with
>
> autoproj rebuild
>
> but it soon fails while compiling typelib, with relevant errors
>
> --------
> [ 61%] Building CXX object
> bindings/ruby/CMakeFiles/__typelib_ruby.dir/ext/value.o
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
> In
> function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE,
> VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:290:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
> In
> function ‘VALUE value_initialize(VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:345:46:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
> In
> function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:512:40:
> error: format not a string literal and no format arguments
> [-Werror=format-security]
> cc1plus: some warnings being treated as errors
> make[2]: ***
> [bindings/ruby/CMakeFiles/__typelib_ruby.dir/ext/value.o]
> Error 1
> make[1]: ***
> [bindings/ruby/CMakeFiles/__typelib_ruby.dir/all] Error 2
> make: *** [all] Error 2
> --------
>
> It seems that in Debian Wheezy, ruby1.9 uses
> -Werror=format-security
> instead of -Wformat-security. The fix for this is to edit the
> typelib/bindings/ruby/ext/__value.cc file as follows:
>
> modify all occurrences of
> rb_raise(rb_eArgError, e.what());
> (which occur on lines 290, 345, 512) as
> rb_raise(rb_eArgError, "%s", e.what());
>
> The same applies to
> typelib/bindings/ruby/ext/__specialized_types.cc on
> lines 54 and 69 and
>
> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/registry.cc
> on lines 166 and 277
>
> After this, autoproj build is successful.
>
>
> Hope this helps,
> Sagar
> --
> Orocos-Users mailing list
> Orocos-Users [..] ... <javascript:;>
> http://lists.mech.kuleuven.be/__mailman/listinfo/orocos-users
> <http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users>
>
>

orocos build fail on debian wheezy

When I had the same problem with that dependency I've found this link
http://www.orocos.org/forum/rtt/rtt-dev/bug-986-new-missing-ncurses-osde...

and fix it with modified appropriate line:
+ <rosdep name="ncurses"/>

After it it starts checking dependency correctly.

Maybe it could also help you but I think removing of line is also good :).

Best Regards,

Sergiy

On 10/08/2012 02:58 PM, Sagar Behere wrote:
> On 10/07/2012 10:44 PM, Peter Soetens wrote:
>>
>> Op zondag 7 oktober 2012 schreef Sagar Behere (sagar [dot] behere [..] ...
>> <mailto:sagar [dot] behere [..] ...>) het volgende:
>>
>> On 10/07/2012 10:24 PM, Peter Soetens wrote:
>>
>> Hi Sagar,
>>
>> There were earlier reports about wheezy. Sylvain has fixed them
>> on the
>> rock branches and they are being prepared to merge on master.
>>
>>
>> Oh, okay.
>>
>> So if you would check the master branches, i believe most issues
>> will be
>> fixed already.
>>
>>
>> When I do 'sh bootstrap.sh' as part of the recommended install
>> procedure, does it pull from the master branches on gitorious? If
>> yes, then the issues weren't fixed as of today afternoon, which is
>> when I faced the issues. If no, could you tell me how to check the
>> master branches?
>>
>>
>> Check the contents of bootstrap.sh, its quite trivial. Just change the
>> toolchain-2.5 argument to master.
> When I switch to branch master and run the installation, it stops at
> some point with the message
>
> ---
> manifest /home/sagar/excludes/orocos-toolchain/ocl/manifest.xml of ocl
> from orocos.toolchain lists 'libncurses-dev' as dependency, but it is
> neither a normal package nor an osdeps package. osdeps reports: there is
> no osdeps definition for libncurses-dev
> ---
>
> libncurses-dev and libncurses5-dev are installed on the system.
> Modifying the ocl/manifest.xml file to make it libncurses5-dev, makes no
> difference. That error still appears, but for libncurses5-dev.
>
> For now, I simply removed the line from the manifest.xml, because I know
> the package is installed and so hopefully the ocl will still compile.
>
> However, the compile halts later with
>
> ------
> [ 94%] Building CXX object lua/CMakeFiles/rttlua-tlsf.dir/rtt.cpp.o
> Linking CXX executable ../../bin/rttlua-corba-gnulinux
> CMakeFiles/rttlua-corba.dir/LuaComponent.cpp.o: In function
> `ORO_main_impl(int, char**)':
> /home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:301:
> undefined reference to
> `OCL::logging::Category::createOCLCategory(std::basic_string<char,
> std::char_traits<char>, std::allocator<char> > const&,
> log4cpp::Category*, int)'
> /home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:301:
> undefined reference to
> `log4cpp::HierarchyMaintainer::set_category_factory(log4cpp::Category*
> (*)(std::basic_string<char, std::char_traits<char>, std::allocator<char>
> > const&, log4cpp::Category*, int))'
> /home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:371:
> undefined reference to
> `log4cpp::HierarchyMaintainer::getDefaultMaintainer()'
> /home/sagar/excludes/orocos-toolchain/ocl/lua/LuaComponent.cpp:372:
> undefined reference to
> `log4cpp::HierarchyMaintainer::getDefaultMaintainer()'
> collect2: ld returned 1 exit status
> ------
>
> This error isn't present in the toolchain-2.5 branch.
>
> Regards,
> Sagar
>
>> Peter
>>
>>
>> Thanks and regards,
>> Sagar
>>
>> Op zondag 7 oktober 2012 schreef Sagar Behere
>> (sagar [dot] behere [..] ...
>> <mailto:sagar [dot] behere [..] ...>) het volgende:
>>
>> On 10/06/2012 10:43 PM, Sagar Behere wrote:
>> > Hello,
>> >
>> > I'm installing orocos on debian wheezy ( following the
>> instructions at
>> >
>> http://www.orocos.org/wiki/__orocos/toolchain/quick-start-__linux <http://www.orocos.org/wiki/orocos/toolchain/quick-start-linux>
>> )
>> >
>> > The output of command: ruby --version is
>> > ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
>> >
>> > after typing: sh bootstrap.sh, the build fails at some point and
>> tells
>> > to look at utilrb-post-install.log for details. A relevant
>> looking
>> > snippet from that file is
>> >
>> > ------
>> > 2012-10-06 22:34:52 +0200: running
>> > rake default
>> > in directory /home/sagar/oroom/orocos-__toolchain/utilrb
>> > INFO: cannot load the Hoe gem. Distribution is disabled
>> > INFO: error message is: cannot load such file -- hoe
>> > creating Makefile
>> > linking shared-object utilrb_ext.so
>> > g++: error: unrecognized command line option ‘-module’
>> > make: *** [utilrb_ext.so] Error 1
>> > rake aborted!
>> > cannot build the C extension
>> > ------
>> >
>> > Any ideas what is wrong and how to fix it?
>>
>> Okay, I found some fixes that work for the above and subsequent
>> problems. These fixes seem to make it compile, but I don't
>> really know
>> what they do (they are a result of long trial and error) so
>> maybe the
>> developers should take a look.
>>
>> It may be that some of the problems occur because Debian
>> Wheezy uses g++
>> version 4.7.1
>>
>> Anyhoo, here are the fixes.
>> ------------------
>> For making utilrb build:
>>
>> gem install hoe
>>
>> edit the utilrb/ext/extconf.rb file and comment out the line
>>
>> $LDFLAGS += " -module"
>>
>> Once this is done, the build can be continued with
>>
>> autoproj rebuild
>>
>> but it soon fails while compiling typelib, with relevant errors
>>
>> --------
>> [ 61%] Building CXX object
>> bindings/ruby/CMakeFiles/__typelib_ruby.dir/ext/value.o
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
>> In
>> function ‘VALUE type_memory_layout(VALUE, VALUE, VALUE,
>> VALUE, VALUE)’:
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:290:40:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
>> In
>> function ‘VALUE value_initialize(VALUE, VALUE)’:
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:345:46:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:
>> In
>> function ‘VALUE typelib_compare(VALUE, VALUE, VALUE)’:
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/value.cc:512:40:
>> error: format not a string literal and no format arguments
>> [-Werror=format-security]
>> cc1plus: some warnings being treated as errors
>> make[2]: ***
>> [bindings/ruby/CMakeFiles/__typelib_ruby.dir/ext/value.o]
>> Error 1
>> make[1]: ***
>> [bindings/ruby/CMakeFiles/__typelib_ruby.dir/all] Error 2
>> make: *** [all] Error 2
>> --------
>>
>> It seems that in Debian Wheezy, ruby1.9 uses
>> -Werror=format-security
>> instead of -Wformat-security. The fix for this is to edit the
>> typelib/bindings/ruby/ext/__value.cc file as follows:
>>
>> modify all occurrences of
>> rb_raise(rb_eArgError, e.what());
>> (which occur on lines 290, 345, 512) as
>> rb_raise(rb_eArgError, "%s", e.what());
>>
>> The same applies to
>> typelib/bindings/ruby/ext/__specialized_types.cc on
>> lines 54 and 69 and
>>
>> /home/sagar/oroom/orocos-__autoproj/typelib/bindings/__ruby/ext/registry.cc
>> on lines 166 and 277
>>
>> After this, autoproj build is successful.
>>
>>
>> Hope this helps,
>> Sagar
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ... <javascript:;>
>> http://lists.mech.kuleuven.be/__mailman/listinfo/orocos-users
>> <http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users>
>>
>>