From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <438B3990.4020809@domain.hid> Date: Mon, 28 Nov 2005 18:08:32 +0100 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-core] Latest snapshot (182) not compiling (kernel) References: <438743FC.6070007@domain.hid> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig62FC64F98006533FB3A51173" List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Panagiotis Issaris Cc: xenomai-core This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig62FC64F98006533FB3A51173 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Panagiotis Issaris wrote: > Hi, >=20 > I'm also having issues compiling the latest Xenomai tree. >=20 >=20 > On 11/25/05, Ignacio Garc=EDa P=E9rez wrote: >> Hi, >> >> I dunno what's changed, but I updated my xenomai snapshot to the lates= t >> revision (182) and the kernel no longer compiles (fails due to some >> xnpod_* undefined symbols). >> >> Revision 179 compiled fine. >=20 >=20 >=20 > I'm using revision 199 on a x86 Ubuntu 5.10 system with GCC 4.0.1 (is a= nyone > else using that one?). >=20 >=20 > LD init/built-in.o > LD .tmp_vmlinux1 > kernel/built-in.o: In function `disengage_irq_shield': > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:176: undefi= ned > reference to `__raw_write_lock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:207: undefi= ned > reference to `__raw_write_unlock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:186: undefi= ned > reference to `__raw_write_unlock' > kernel/built-in.o: In function `xnshadow_reset_shield': > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:152: undefi= ned > reference to `__raw_read_lock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:158: undefi= ned > reference to `__raw_read_unlock' > kernel/built-in.o: In function `lostage_handler': > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:152: undefi= ned > reference to `__raw_read_lock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:158: undefi= ned > reference to `__raw_read_unlock' > kernel/built-in.o: In function `xnshadow_relax': > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:152: undefi= ned > reference to `__raw_read_lock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:158: undefi= ned > reference to `__raw_read_unlock' > kernel/built-in.o: In function `schedule_event': > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:152: undefi= ned > reference to `__raw_read_lock' > /usr/local/src/linux-2.6.14/kernel/xenomai/nucleus/shadow.c:158: undefi= ned > reference to `__raw_read_unlock' > make[1]: *** [.tmp_vmlinux1] Error 1 > make: *** [_all] Error 2 >=20 Kernel config...? Do you happen to have the IRQ shield switched on? May it's a regression related to this per-default-off feature. Jan --------------enig62FC64F98006533FB3A51173 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 iD8DBQFDizmQncNeS9Q0k+IRArStAJ9a7odLSbCSFwru13hwBYrauedNEgCgxABT xrbeYi2ajPgv2PQonrBbruY= =+pyj -----END PGP SIGNATURE----- --------------enig62FC64F98006533FB3A51173--