[255] in arla-drinkers
Re: arla 0.9 : cannot compile on linux
daemon@ATHENA.MIT.EDU (Love)
Tue Sep 15 11:16:56 1998
From owner-arla-drinkers@stacken.kth.se Tue Sep 15 15:16:56 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 25387 invoked from network); 15 Sep 1998 15:16:55 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 15 Sep 1998 15:16:55 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA12871
for arla-drinkers-list; Tue, 15 Sep 1998 17:09:05 +0200 (MET DST)
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA12854
for <arla-drinkers@stacken.kth.se>; Tue, 15 Sep 1998 17:09:00 +0200 (MET DST)
Received: from hummel.e.kth.se (hummel.e.kth.se [130.237.43.135])
by elixir.e.kth.se (8.8.7/8.8.7) with ESMTP id RAA30731;
Tue, 15 Sep 1998 17:08:58 +0200 (MET DST)
Received: (lha@localhost) by hummel.e.kth.se (8.8.7/8.6.6) id RAA26476; Tue, 15 Sep 1998 17:08:48 +0200 (MET DST)
To: mc8644.com@mclink.it
Cc: arla-drinkers@stacken.kth.se
Subject: Re: arla 0.9 : cannot compile on linux
References: <35FE7DFB.27900453@mclink.it>
From: Love <lha@elixir.e.kth.se>
Date: 15 Sep 1998 17:08:48 +0200
In-Reply-To: mc8644.com@mclink.it's message of Tue, 15 Sep 1998 16:47:23 +0200
Message-ID: <amn281mn0f.fsf@hummel.e.kth.se>
Lines: 72
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
mc8644.com@mclink.it writes:
> Hello. I have downoaded arla 0.9 willing to try it on some linux boxes,
> but I cannot compile it. I have tried the usual ./configure ; make , and have
> also changed several times the various configure parameters (directory, etc.)
> to no avail.
> The compilation dies on two different machines that work normally,
> therefore I would conclude that there is some problem wit arla itself.
>
> ....
> make[2]: Entering directory `/incoming/arla-0.9/xfs/linux'
> gcc -c -DHAVE_CONFIG_H -DMODULE -DMODVERSIONS -D__KERNEL__ -DDEBUG -I.
> -I. -g -Wall -g -I. -I./../include -I../../include -I./../../include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer xfs_load.c
> In file included from xfs_load.c:39:
> xfs_locl.h:47: linux/modversions.h: No such file or directory
Try this patch:
Index: configure.in
===================================================================
RCS file: /usr/local/cvsroot/arla/configure.in,v
retrieving revision 1.158
retrieving revision 1.159
diff -u -w -r1.158 -r1.159
--- configure.in 1998/09/15 00:52:46 1.158
+++ configure.in 1998/09/15 14:56:55 1.159
@@ -448,7 +448,7 @@
AC_CHECK_HEADERS(nlist.h libelf/nlist.h resolv.h kvm.h)
dnl Linux specific __kernel_* types
-AC_CHECK_HEADERS(linux/types.h)
+AC_CHECK_HEADERS(linux/types.h linux/modversions.h)
dnl Make sure we get config.h
if test "$KRB_INC_DIR"; then
RCS file: /usr/local/cvsroot/arla/xfs/linux/xfs_locl.h,v
retrieving revision 1.15
diff -u -w -r1.15 xfs_locl.h
--- xfs_locl.h 1998/07/19 01:24:38 1.15
+++ xfs_locl.h 1998/09/15 14:54:20
@@ -44,7 +44,9 @@
#endif
#include <linux/version.h>
+#ifdef HAVE_LINUX_MODVERSIONS_H
#include <linux/modversions.h>
+#endif
#include <linux/errno.h>
#include <linux/fs.h>
#include <linux/malloc.h>
You have to run autoreconf i the source top directory and rerun configure
to get the configure.in patch to accully do thing.
> gcc -c -DHAVE_CONFIG_H -DSYSCONFDIR=\"/usr/arla/etc\" -DARLACACHEDIR=\"/usr/arl
> a/cache\" -DARLACONFFILE=\"/usr/arla/etc/arla.conf\" -I. -I. -I./.. -I/home/nico
> la/arla-0.9/xfs/linux -I../include -I./../include -I../rxdef -I./../rxkad -DDEB
> UG -g -Wall messages.c
> messages.c: In function `xfs_message_getroot':
> messages.c:552: `RXKADEXPIRED' undeclared (first use this function)
> messages.c:552: (Each undeclared identifier is reported only once
Do you have kerberos (like http://www.pdc.kth.se/kthkrb/) installed,
it doesn't seem that way on the includes. (rxkad depend on it, and
the error codes are in rxkad/rxkad.h, I guess they could be broken out).
The simple solution (for us) is that you install kerberos ;)
Love
