From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44ECB384.8080000@domain.hid> Date: Wed, 23 Aug 2006 21:59:00 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-core] Problems building RTnet References: <200608232058.36523.niklaus.giger@domain.hid> In-Reply-To: <200608232058.36523.niklaus.giger@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDE2E193ADFC4C32B77F8766D" Sender: jan.kiszka@domain.hid List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: niklaus.giger@domain.hid Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDE2E193ADFC4C32B77F8766D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Niklaus Giger wrote: > Hi=20 >=20 > Since a few hours RTnet cannot even be configured, as the Xenomai versi= on got > bumped to 2.3-devel. See > http://ngiger.dyndns.org/buildbot/tqm860/builds/8/step-cfg_RTnet/0 > Where it says: >=20 > checking for Xenomai version... configure: error: *** Unsupported Xenom= ai=20 > version 2.3-devel in /var/buildbot/slave/tqm860/linux Fixed (for the next versions now as well...). >=20 > 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__ -Wa= ll -pipe -I../../../stack/include -I../../../stack/include -g -MT=20 > rtnet_ifs.o -MD -MP -MF ".deps/rtnet_ifs.Tpo" -c -o rtnet_ifs.o rtnet_i= fs.c;=20 > \ > then mv -f ".deps/rtnet_ifs.Tpo" ".deps/rtnet_ifs.Po"; else=20 > 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 dire= ctory 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 --------------enigDE2E193ADFC4C32B77F8766D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE7LOEniDOoMHTA+kRAks2AJ4gigbUT7jFn7EnOsM3muC96o6NhACffg50 uOAQ/BmINXGu1GcOWY7/U6I= =bn2g -----END PGP SIGNATURE----- --------------enigDE2E193ADFC4C32B77F8766D--