* [Xenomai-core] Problems building RTnet
@ 2006-08-23 18:58 Niklaus Giger
2006-08-23 19:59 ` Jan Kiszka
0 siblings, 1 reply; 4+ messages in thread
From: Niklaus Giger @ 2006-08-23 18:58 UTC (permalink / raw)
To: xenomai
Hi
Since a few hours RTnet cannot even be configured, as the Xenomai version got
bumped to 2.3-devel. See
http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0
Where it says:
checking for Xenomai version... configure: error: *** Unsupported Xenomai
version 2.3-devel in /var/buildbot/slave/tqm860/linux
This morning the buildbot complained like the following:
powerpc-860-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../config -g -I. -I/usr/xenomai/include -g -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -I../../../stack/include -I../../../stack/include -g -MT
rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_ifs.c;
\
then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else
rm -f ".deps/rtnet_ifs.Tpo"; exit 1; fi
In file included from rtnet_ifs.c:31:
../../../stack/include/rtnet.h:29:23: rtdm/rtdm.h: No such file or directory
rtnet_ifs.c: In function `main':
rtnet_ifs.c:51: warning: implicit declaration of function `rt_dev_socket'
rtnet_ifs.c:61: warning: implicit declaration of function `rt_dev_ioctl'
rtnet_ifs.c:61: error: `SIOCGIFCONF' undeclared (first use in this function)
rtnet_ifs.c:61: error: (Each undeclared identifier is reported only once
rtnet_ifs.c:61: error: for each function it appears in.)
rtnet_ifs.c:63: warning: implicit declaration of function `rt_dev_close'
rtnet_ifs.c:73: error: `SIOCGIFFLAGS' undeclared (first use in this function)
rtnet_ifs.c:83: error: `SIOCGIFINDEX' undeclared (first use in this function)
make[4]: *** [rtnet_ifs.o] Fehler 1
Best regards
--
Niklaus Giger
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai-core] Problems building RTnet
2006-08-23 18:58 [Xenomai-core] Problems building RTnet Niklaus Giger
@ 2006-08-23 19:59 ` Jan Kiszka
2006-08-23 20:17 ` Jan Kiszka
0 siblings, 1 reply; 4+ messages in thread
From: Jan Kiszka @ 2006-08-23 19:59 UTC (permalink / raw)
To: niklaus.giger; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Niklaus Giger wrote:
> Hi
>
> Since a few hours RTnet cannot even be configured, as the Xenomai version got
> bumped to 2.3-devel. See
> http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0
> Where it says:
>
> checking for Xenomai version... configure: error: *** Unsupported Xenomai
> version 2.3-devel in /var/buildbot/slave/tqm860/linux
Fixed (for the next versions now as well...).
>
> This morning the buildbot complained like the following:
> powerpc-860-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../config -g -I. -I/usr/xenomai/include -g -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -I../../../stack/include -I../../../stack/include -g -MT
> rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_ifs.c;
> \
> then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else
> rm -f ".deps/rtnet_ifs.Tpo"; exit 1; fi
> In file included from rtnet_ifs.c:31:
> ../../../stack/include/rtnet.h:29:23: rtdm/rtdm.h: No such file or directory
There must be still something wrong with the xenomai user-space
installation. Check if the xeno-config handed to RTnet returns
reasonable paths and if those paths contain the files we need here.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai-core] Problems building RTnet
2006-08-23 19:59 ` Jan Kiszka
@ 2006-08-23 20:17 ` Jan Kiszka
2006-08-23 20:49 ` Philippe Gerum
0 siblings, 1 reply; 4+ messages in thread
From: Jan Kiszka @ 2006-08-23 20:17 UTC (permalink / raw)
To: niklaus.giger; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Jan Kiszka wrote:
> Niklaus Giger wrote:
>> Hi
>>
>> Since a few hours RTnet cannot even be configured, as the Xenomai version got
>> bumped to 2.3-devel. See
>> http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0
>> Where it says:
>>
>> checking for Xenomai version... configure: error: *** Unsupported Xenomai
>> version 2.3-devel in /var/buildbot/slave/tqm860/linux
>
> Fixed (for the next versions now as well...).
>
>> This morning the buildbot complained like the following:
>> powerpc-860-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../config -g -I. -I/usr/xenomai/include -g -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -I../../../stack/include -I../../../stack/include -g -MT
>> rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_ifs.c;
>> \
>> then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else
>> rm -f ".deps/rtnet_ifs.Tpo"; exit 1; fi
>> In file included from rtnet_ifs.c:31:
>> ../../../stack/include/rtnet.h:29:23: rtdm/rtdm.h: No such file or directory
>
> There must be still something wrong with the xenomai user-space
> installation. Check if the xeno-config handed to RTnet returns
> reasonable paths and if those paths contain the files we need here.
>
Looks like a DESTDIR-or-not-DESTDIR question in the include (and lib?)
paths xeno-config returns. Do we need two runs for the Xenomai lib
installation, one for the target and one for the build host? Or is RTnet
supposed to add DESTDIR to all paths returned by xeno-config? Tricky,
too tricky for tonight.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai-core] Problems building RTnet
2006-08-23 20:17 ` Jan Kiszka
@ 2006-08-23 20:49 ` Philippe Gerum
0 siblings, 0 replies; 4+ messages in thread
From: Philippe Gerum @ 2006-08-23 20:49 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
On Wed, 2006-08-23 at 22:17 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Niklaus Giger wrote:
> >> Hi
> >>
> >> Since a few hours RTnet cannot even be configured, as the Xenomai version got
> >> bumped to 2.3-devel. See
> >> http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0
> >> Where it says:
> >>
> >> checking for Xenomai version... configure: error: *** Unsupported Xenomai
> >> version 2.3-devel in /var/buildbot/slave/tqm860/linux
> >
> > Fixed (for the next versions now as well...).
> >
> >> This morning the buildbot complained like the following:
> >> powerpc-860-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../config -g -I. -I/usr/xenomai/include -g -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -I../../../stack/include -I../../../stack/include -g -MT
> >> rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_ifs.c;
> >> \
> >> then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else
> >> rm -f ".deps/rtnet_ifs.Tpo"; exit 1; fi
> >> In file included from rtnet_ifs.c:31:
> >> ../../../stack/include/rtnet.h:29:23: rtdm/rtdm.h: No such file or directory
> >
> > There must be still something wrong with the xenomai user-space
> > installation. Check if the xeno-config handed to RTnet returns
> > reasonable paths and if those paths contain the files we need here.
> >
>
> Looks like a DESTDIR-or-not-DESTDIR question in the include (and lib?)
> paths xeno-config returns. Do we need two runs for the Xenomai lib
> installation, one for the target and one for the build host? Or is RTnet
> supposed to add DESTDIR to all paths returned by xeno-config? Tricky,
> too tricky for tonight.
$ DESTDIR=/foo xeno-config ...
would make xeno-config prepend the staging directory to the output paths
when appropriate.
>
> Jan
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-08-23 20:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-23 18:58 [Xenomai-core] Problems building RTnet Niklaus Giger
2006-08-23 19:59 ` Jan Kiszka
2006-08-23 20:17 ` Jan Kiszka
2006-08-23 20:49 ` Philippe Gerum
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.