Re: OCL on master no longer building

Ruben Smits <[email protected]>
Newsgroups gmane.science.robotics.orocos.devel
Message-ID <CAN8Phbmf_HuH8j6QczTkd2-Y+BpC+RVyO4LPp4noObeknMw+MA@mail.gmail.com>
On Sun, Oct 20, 2013 at 3:47 PM, Peter Soetens <[email protected]> wrote:
> Hi,
>
> OCL is currently not building on master because of what I believe is
> it's looking for RTT 2.7.0 while the master branch of RTT says its
> 2.6.0 :
>
> [31m [1m  ERROR: got an error processing ocl, waiting for pending jobs
> to end [0m
>
>  [1m [31mBuild failed [0m
>
>  [1m [31mocl(<http://vader:8080/jenkins/job/bootstrap-toolchain-ros/./CORBA_IMPL=TAO,TARGET=gnulinux,arch=amd64,branch=master/ws/orocos-toolchain/ocl)>:
> failed in configure phase [0m
>
>     'cmake -DCMAKE_INSTALL_PREFIX=<http://vader:8080/jenkins/job/bootstrap-toolchain-ros/./CORBA_IMPL=TAO,TARGET=gnulinux,arch=amd64,branch=master/ws/orocos-toolchain/install>
> -DCMAKE_MODULE_PATH= -DOROCOS_TARGET=gnulinux
> <http://vader:8080/jenkins/job/bootstrap-toolchain-ros/./CORBA_IMPL=TAO,TARGET=gnulinux,arch=amd64,branch=master/ws/orocos-toolchain/ocl'>
> returned status 1 [0m
>
>     see <http://vader:8080/jenkins/job/bootstrap-toolchain-ros/./CORBA_IMPL=TAO,TARGET=gnulinux,arch=amd64,branch=master/ws/orocos-toolchain/install/log/ocl-configure.log>
> for details [0m
>
>     last 10 lines are: [0m
>
>           RTT not found: [0m
>
>        * Is the version correct (2.7.0 or higher) ? [0m
>
>        * Did you build & install it ? [0m
>
>        * Did you source env.sh ? [0m
>

Merged catkin branch into master, should be fixed now!

R.


> Peter
> --
> Orocos-Dev mailing list
> [email protected]
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev



-- 
Ruben Smits, CTO
+32 479 511 786
Intermodalics - Kapeldreef 60, 3001 Heverlee - BELGIUM
www.intermodalics.eu
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.