Re: [Xenomai-core] Buildbot: Errors building rtnet since at least r1834

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 5741 bytes --]

Niklaus Giger wrote:
> Am Samstag, 18. November 2006 19:00 schrieb Jan Kiszka:
>> Niklaus Giger wrote:
>>> Hi
>>>
>>> Unfortunately I cannot say since when this build is broken, as I had to
>>> reinstall the buildbot on my main server. But this particular build
>>> target should not have been affected. (Same compiler, same build slave,
>>> same scripts)
>>>
>>> But since at November 12 I get the following errors in my builds:
>>> See http://ngiger.dyndns.org/buildbot-full/tqm_f/builds/0/step-mk_RTnet/1
>>> libtool: link: warning: library
>>> `/var/buildbot/install/tqm_f-r1834/usr/xenomai/lib/libpthread_rt.la' was
>>> moved.
>>> libtool: link: warning: library
>>> `/var/buildbot/install/tqm_f-r1834/usr/xenomai/lib/librtdm.la' was moved.
>>> libtool: link: warning: library
>>> `/var/buildbot/install/tqm_f-r1834/usr/xenomai/lib/libpthread_rt.la' was
>>> moved.
>>> libtool: link: warning: library
>>> `/var/buildbot/install/tqm_f-r1834/usr/xenomai/lib/librtdm.la' was moved.
>>>
>>> Has anybody a hint, what the reason could be?
>> DESTDIR issue? Are you compiling both Xenomai and RTnet with the same
>> DESTDIR?
> Calling manuall make install like the following line did not change the 
> result:
> DESTDIR=/var/buildbot/install/tqm_q make prefix=/var/buildbot/install/tqm_q 
> install 

make install of ...? Also, the prefix is not needed unless you modify
the layout *on the target*.

> 
> My steps to compile the xenomai kernel were:
> cd /var/buildbot/slave/tqm_q/linux
> export CROSS_COMPILE=powerpc-860-linux-gnu- 
> make oldconfig
> make --jobs=4 uImage modules
> make INSTALL_MOD_PATH=/var/buildbot/install/tqm_q modules_install
> make DESTDIR=/var/buildbot/install/tqm_q install

[has no influence here]

> cd /var/buildbot/slave/tqm_q/build
> ../xenomai/configure --host=ppc-linux --enable-debug
> make 

No install? I'll assume there is one with DESTDIR passed appropriately,
right?

> cd /var/buildbot/slave/tqm_q/rtnet
> ./configure --host=powerpc-860-linux-gnu --enable-rtwlan --enable-route-src --enable-net-routing --enable-router --enable-rtcfg-dbg --enable-nomac --enable-rtcap --enable-proxy --enable-examples --enable-checks --enable-fec-enet --enable-scc-enet --with-rtext-config=/var/buildbot/install/tqm_q/usr/xenomai/bin/xeno-config --with-linux=../linux --prefix=/var/buildbot/install/tqm_q 
> DESTDIR=/var/buildbot/install/tqm_q
> make prefix=/var/buildbot/install/tqm_q install
> 
> Is this okay? Or do I have an error here?

DESTDIR belongs to which command?

In any case, ./configure needs it in order to get the correct paths from
xeno-config, and make install requires it, as usual, too. So it's likely
best to simply export DESTDIR before starting the whole batch.

> 
> Isn't it more the problem that xeno-config since a few weeks ago outputs wrong 
> paths (forgets about its DESTDIR when installed). E.g. look at this output of
> /var/buildbot/install/tqm_q/usr/xenomai/bin/xeno-config
> xeno-config --verbose
>     --version="2.2.91"
>     --cc="gcc"
>     --arch="powerpc"
>     --prefix="/usr/xenomai"
>     --xeno-cflags="-I/usr/xenomai/include -D_GNU_SOURCE -D_REENTRANT"
>     --xeno-ldflags="-L/usr/xenomai/lib -lpthread "
>     --posix-cflags="-I/usr/xenomai/include -I/usr/xenomai/include/posix -D_GNU_SOURCE -D_REENTRANT -D__XENO__"
>     --posix-ldflags="-L/usr/xenomai/lib -lpthread_rt -lpthread -lrt "
>     --library-dir="/usr/xenomai/lib"
> 
> I think --xeno-ldflags="-L/usr/xenomai/lib -lpthread " should return
> --xeno-ldflags="-L/var/buildbot/install/usr/xenomai/lib -lpthread "

That's correct. Note that xeno-config is first of all intended to run on
the *target* and provide correct paths there. To use it also on the
build host, you have to invoke it with DESTDIR set appropriately (see
above).

> 
> 
>> Check what's stated in those .la files and compare with the RTnet build
>> parameters.
> *.la files are attached
>> Jan
>>
>> PS: This is a *warning*, not a fatal *error*. Or did you just want to
>> receive more attention? ;)
> Sorry. I forgot to include the line with the real error.
> 
> powerpc-860-linux-gnu-gcc -I/var/buildbot/install/tqm_q/usr/xenomai/include -I/var/buildbot/install/tqm_q/usr/xenomai/include/posix -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -O2 -fstrict-aliasing -I../../../stack/include -g -Wl,@/var/buildbot/install/tqm_q/usr/xenomai/lib/posix.wrappers -o 
> rtt-sender 
> rtt-sender.o  -L/var/buildbot/install/tqm_q/usr/xenomai/lib /var/buildbot/install/tqm_q/usr/xenomai/lib/libpthread_rt.so -lrt -lpthread /var/buildbot/install/tqm_q/usr/xenomai/lib/librtdm.so -Wl,--rpath -Wl,/var/buildbot/install/tqm_q/usr/xenomai/lib -Wl,--rpath -Wl,/var/buildbot/install/tqm_q/usr/xenomai/lib
> /opt/crosstool/gcc-3.4.1-glibc-2.3.3/powerpc-860-linux-gnu/lib/gcc/powerpc-860-linux-gnu/3.4.1/../../../../powerpc-860-linux-gnu/bin/ld: 
> @/var/buildbot/install/tqm_q/usr/xenomai/lib/posix.wrappers: No such file: No 
> such file or directory
> collect2: ld returned 1 exit status

Is /var/buildbot/install/tqm_q/usr/xenomai/lib/posix.wrappers the
correct path? Does the file exist?

...
> 
> # Directory that this library needs to be installed in:
> libdir='/usr/xenomai/lib'

That's ok from the target's POV. Unfortunately, we then see those "was
moved" warnings. I don't know if one can avoid them via some magic, but
they are harmless.

@All: Does anyone know how to pass a prefix (DESTDIR) to an
automake-based linking step - and how to code this into .am files? The
scenario is linking against libs (represented via .la files) that were
installed for the target, i.e. without the DESTDIR part the host needs.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]