[975] in arla-drinkers
Problem starting arla on OpenBSD 2.5
daemon@ATHENA.MIT.EDU (Bjorn Lindgren)
Thu Jul 15 05:16:32 1999
From owner-arla-drinkers@stacken.kth.se Thu Jul 15 09:16:31 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 10245 invoked from network); 15 Jul 1999 09:16:31 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 15 Jul 1999 09:16:31 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id LAA02725
for arla-drinkers-list; Thu, 15 Jul 1999 11:05:12 +0200 (MET DST)
Received: from birdie.sekure.net (nr@sekure.net [193.15.98.64])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id LAA02721
for <arla-drinkers@stacken.kth.se>; Thu, 15 Jul 1999 11:05:08 +0200 (MET DST)
Received: from localhost (nr@localhost)
by birdie.sekure.net (Sekure.Net Mailer) with ESMTP id LAA27696
for <arla-drinkers@stacken.kth.se>; Thu, 15 Jul 1999 11:05:51 +0200 (CEST)
Date: Thu, 15 Jul 1999 11:05:51 +0200 (CEST)
From: Bjorn Lindgren <nr@birdie.sekure.net>
To: arla-drinkers@stacken.kth.se
Subject: Problem starting arla on OpenBSD 2.5
Message-ID: <Pine.BSO.4.10.9907151056300.6956-100000@birdie.sekure.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Hi, have have some serious problems then trying to start Arla on my
OpenBSD 2.5 system using the standard kernel. Then I run 'startarla' I get
these error messages, I get the same errors then trying to manualy load
the xfs_mod.o module with 'modload'. It seams to build ok, only minor
compile warnings. The Arla package version is 0.26 and I get the same
errors with 0.25 and 0.24 .
bash-2.03# startarla
xfs_message.c:190: Undefined symbol `_VOP_UNLOCK' referenced from text
segment
xfs_syscalls-common.c:287: Undefined symbol `_VOP_GETATTR' referenced from
text segment
xfs_vfsops-common.c:125: Undefined symbol `_VOP_GETATTR' referenced from
text segment
xfs_vfsops-bsd.c:297: Undefined symbol `_VOP_GETATTR' referenced from text
segment
xfs_vfsops-bsd.c:348: Undefined symbol `_VOP_OPEN' referenced from text
segment
xfs_vfsops-bsd.c:375: Undefined symbol `_VOP_UNLOCK' referenced from text
segment
xfs_vnodeops-common.c:258: Undefined symbol `_VOP_READ' referenced from
text segment
xfs_vnodeops-common.c:259: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
xfs_vnodeops-common.c:280: Undefined symbol `_VOP_WRITE' referenced from
text segment
xfs_vnodeops-common.c:282: Undefined symbol `_VOP_GETATTR' referenced from
text segment
xfs_vnodeops-common.c:291: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
xfs_vnodeops-common.c:436: Undefined symbol `_VOP_ACCESS' referenced from
text segment
xfs_vnodeops-common.c:706: Undefined symbol `_VOP_READ' referenced from
text segment
xfs_vnodeops-common.c:709: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
xfs_vnodeops-common.c:797: Undefined symbol `_VOP_READ' referenced from
text segment
xfs_vnodeops-common.c:798: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
xfs_vnodeops-common.c:829: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
xfs_vnodeops-bsd.c:529: Undefined symbol `_VOP_ABORTOP' referenced from
text segment
xfs_vnodeops-bsd.c:533: Undefined symbol `_VOP_ABORTOP' referenced from
text segment
xfs_vnodeops-bsd.c:537: Undefined symbol `_VOP_ABORTOP' referenced from
text segment
xfs_vnodeops-bsd.c:555: Undefined symbol `_VOP_UNLOCK' referenced from
text segment
modload: /usr/bin/ld: return code 1
mount_xfs: mount: Operation not supported by device
