orocreate-pkg crashes and "make install" does not work any more

Submitted by joergwl on Sat, 2011-06-18 15:12

Hi all,

I checked out toolchain 2.4 today and when I call "orocreate-pkg Test" I get the message: "/opt/orocos/install/bin/orocreate-pkg: Zeile 125: [: Zu viele Argumente."

The reason for me to try this in the first place was that I was not able to install my own packages any more (after I did the update this morning)

My installation is at "/opt/orocos/install" When I call "make install" I get

CMake Error at src/cmake_install.cmake:42 (FILE): file cannot create directory: /usr/local/lib/orocos/gnulinux/ConfigHandler. Maybe need administrative privileges. Call Stack (most recent call first): cmake_install.cmake:37 (INCLUDE)

This was working fine until I made the update. I deleted orocos completely and check it out clean but the trouble stays.

Meanwhile I have the impression that the build system is more complex and error prone as the software it self....

Ciao Joerg

orocreate-pkg crashes and "make install" does not work any more

Submitted by snrkiwi on Sat, 2011-06-18 15:40.

On Jun 18, 2011, at 11:12 , joerg [..] ... wrote:

> Hi all,
>
> I checked out toolchain 2.4 today and when I call "orocreate-pkg Test" I get the message: "/opt/orocos/install/bin/orocreate-pkg: Zeile 125: [: Zu viele Argumente."
>
> The reason for me to try this in the first place was that I was not able to install my own packages any more (after I did the update this morning)
>
> My installation is at "/opt/orocos/install"
> When I call "make install" I get
>
> CMake Error at src/cmake_install.cmake:42 (FILE):
> file cannot create directory: /usr/local/lib/orocos/gnulinux/ConfigHandler.
> Maybe need administrative privileges.
> Call Stack (most recent call first):
> cmake_install.cmake:37 (INCLUDE)
>
> This was working fine until I made the update.
> I deleted orocos completely and check it out clean but the trouble stays.
>
> Meanwhile I have the impression that the build system is more complex and error prone as the software it self....

I don't think you're wrong ... actually, if you analyzed the ML traffic in recent months, I suspect that you would find that problems with the build system(s) far outweigh problems with the software itself ... :-(
S

Re: orocreate-pkg crashes and "make install" does not work...

Submitted by joergwl on Sat, 2011-06-18 15:50.

snrkiwi wrote:

On Jun 18, 2011, at 11:12 , joerg [..] ... wrote:

> Hi all, > > I checked out toolchain 2.4 today and when I call "orocreate-pkg Test" I get the message: "/opt/orocos/install/bin/orocreate-pkg: Zeile 125: [: Zu viele Argumente." > > The reason for me to try this in the first place was that I was not able to install my own packages any more (after I did the update this morning) > > My installation is at "/opt/orocos/install" > When I call "make install" I get > > CMake Error at src/cmake_install.cmake:42 (FILE): > file cannot create directory: /usr/local/lib/orocos/gnulinux/ConfigHandler. > Maybe need administrative privileges. > Call Stack (most recent call first): > cmake_install.cmake:37 (INCLUDE) > > This was working fine until I made the update. > I deleted orocos completely and check it out clean but the trouble stays. > > Meanwhile I have the impression that the build system is more complex and error prone as the software it self....

It's a pity ... . I think orocos it self is pretty cool stuff (that's why I want to use it)...

I really wonder what I would give up if I skip the Cmake stuff and just link the libs I need directly??

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows

orocreate-pkg crashes and "make install" does not work any more

Submitted by peter on Sat, 2011-06-18 20:28.

On Sat, Jun 18, 2011 at 5:12 PM, <joerg [..] ...> wrote:
> Hi all,
>
> I checked out toolchain 2.4 today and when I call "orocreate-pkg Test" I get the message: "/opt/orocos/install/bin/orocreate-pkg: Zeile 125: [: Zu viele Argumente."

I pushed a fix for this. Checkout the new functionality of the script
with orocreate-pkg --help...

>
> The reason for me to try this in the first place was that I was not able to install my own packages any more (after I did the update this morning)
>
> My installation is at "/opt/orocos/install"
> When I call "make install" I get
>
> CMake Error at src/cmake_install.cmake:42 (FILE):
> file cannot create directory: /usr/local/lib/orocos/gnulinux/ConfigHandler.
> Maybe need administrative privileges.
> Call Stack (most recent call first):
> cmake_install.cmake:37 (INCLUDE)

It looks like the CMAKE_INSTALL_PREFIX has been changed (can you check
the build/CMakeCache.txt) ? Are you using autoproj to manage these
packages or plain UseOrocos-RTT.cmake + make ?

We had one patch related to install locations, but that only
influenced win32 targets... So I'm still puzzled why this has occured.
The only thing influencing the installation location is
CMAKE_INSTALL_PREFIX and we don't play with that variable, except on
win32...

>
> This was working fine until I made the update.
> I deleted orocos completely and check it out clean but the trouble stays.

Doing such a drastic step while sticking on the same branch should
never be necessary...

>
> Meanwhile I have the impression that the build system is more complex and error prone as the software it self....

We're in a 3-way split-position here. It's autoproj vs plain make vs
rosmake + try to support this on N platforms. We've come a long way
though...

Peter

orocreate-pkg crashes and "make install" does not work any more

Submitted by joergwl on Sun, 2011-06-19 11:50.

> We're in a 3-way split-position here. It's autoproj vs plain make vs > rosmake + try to support this on N platforms. We've come a long way > though...

Don't get me wrong I certainly don't want to blame anyone ....

I personally find it harder to dig around in complex scripting stuff than digging in C/C++ code. Especially when there is no debugger at hand which allows tracing step by step. Means you have really to understand whats going on and can't just look where a certain value is coming from or gets changed....

when I looked some years ago on orocos it was using cmake for configuration of it self, and the application could just use what ever you where fancy about. Means just make in my case. Using cmake for the application is cool if all works well, for me a nightmare if something goes wrong. It means I have to learn how cmake ticks(what is inbuild, what must be a macro defined elsewhere), and where all the settings are coming from, to figure out what I could have made wrong, its just not obvious any more....

On the other hand I highly appreciate your help, even if some of my problems may look rather stupid...

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows

Hi Peter,I don't use

Submitted by joergwl on Sun, 2011-06-19 11:31.

Hi Peter,

I don't use autoproj for my packages, just cmake and make. You can see what I exactly do from the template package I have posted in another thread. Thats the base for all my packages. I used basically the source from orocreat-pkg and extend it by sub-dirs for test, src, include and introduced a separation of interface and implementation.

Attached is the CMakeCache.txt

My makefile is:

  all:
    mkdir -p build
    cd build ; cmake .. -DINSTALL_PATH=orocos -DCMAKE_BUILD_TYPE=$(CMAKE_BUILD_TYPE) && make -j
    echo -e "\n Now do 'make install' to install this package.\n"
  install: all
    cd build ; make install   
  clean:
    rm -rf build

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows

Hi Peter,creating a new

Submitted by joergwl on Sun, 2011-06-19 11:20.

Hi Peter,

creating a new package with "orocreate-pkg TestPack component" worked, however build this package does not work as there are some names (@pkgname@) not replaced in CMakeLists.txt (see attachment)

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows

Hi Peter,creating a new

Submitted by peter on Mon, 2011-06-20 15:12.

On Sun, Jun 19, 2011 at 1:20 PM, <joerg [..] ...> wrote:
> Hi Peter,
>
> creating a new package with "orocreate-pkg TestPack component" worked,
> however build this package does not work as there are some names (@pkgname@)
> not replaced in CMakeLists.txt

Ouch :-] another job for Jenkins to check. I've pushed the fix.

Peter

Hi Peter,creating a new

Submitted by joergwl on Tue, 2011-06-21 09:13.

I checked out freshly again (git://gitorious.org/orocos-toolchain/build.git release=toolchain-2.4)

Now creating an new package with orocreate-pkg works fine also compiling and installing works.

However when I start the deployer-gnulinux withaout any options, after I installed the new created package, I the output:

 0.013 [ ERROR  ][Logger] could not load library
 '/opt/orocos/install/lib/orocos/./types/libMyPack-transport-mqueue-gnulinux.so': 
 libMyPack- typekit-gnulinux.so: cannot open shared object file: No such file or directory
 0.013 [ ERROR  ][Logger] could not load library
 '/opt/orocos/install/lib/orocos/./types/libMyPack-transport-corba-gnulinux.so': 
 libMyPack-typekit-gnulinux.so: cannot open shared object file: No such file or directory
 0.126 [ Warning][Logger] Some found plugins could not be loaded !
 0.126 [ Warning][Logger] Corrupted files found in '/opt/orocos/install/lib/orocos'. Fix or remove these plugins.
 0.130 [ ERROR  ][TypekitRepository::Import] A protocol with id 2 was already added for type array
 0.133 [ ERROR  ][TypekitRepository::Import] A protocol with id 1 was already added for type string 
 0.133 [ ERROR  ][TypekitRepository::Import] A protocol with id 1 was already added for type array
 Switched to : Deployer

Whats this??

Again, I just compiled and installed the package created by "orocreate-pkg MyPack" and started the deployer right afterwards.. .. .

Ciao Joerg

Computer are like air conditioner, they stop working properly when opening windows