[1068] in arla-drinkers
Arla 0.26/27pre4 vs. Linux 2.2.10 on SparcUltra 5
daemon@ATHENA.MIT.EDU (Tobias Grundmann)
Fri Aug 13 09:31:13 1999
From owner-arla-drinkers@stacken.kth.se Fri Aug 13 13:31:12 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 4994 invoked from network); 13 Aug 1999 13:31:11 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 13 Aug 1999 13:31:11 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id PAA10550
for arla-drinkers-list; Fri, 13 Aug 1999 15:18:23 +0200 (MET DST)
Received: from peanuts.informatik.uni-tuebingen.de (peanuts.Informatik.Uni-Tuebingen.De [134.2.14.1])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id PAA10503
for <arla-drinkers@stacken.kth.se>; Fri, 13 Aug 1999 15:18:12 +0200 (MET DST)
Received: from peanuts.informatik.uni-tuebingen.de (carthy [134.2.14.21])
by peanuts.informatik.uni-tuebingen.de (8.9.1/8.9.1/PEANUTS Revision: 1.1 $) with ESMTP id PAA25526
for <arla-drinkers@stacken.kth.se>; Fri, 13 Aug 1999 15:18:06 +0200 (MET DST)
Message-Id: <199908131318.PAA25526@peanuts.informatik.uni-tuebingen.de>
X-Mailer: exmh version 2.0.2 2/24/98
To: arla-drinkers@stacken.kth.se
Subject: Arla 0.26/27pre4 vs. Linux 2.2.10 on SparcUltra 5
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 13 Aug 1999 15:19:23 +0200
From: Tobias Grundmann <grundman@Informatik.Uni-Tuebingen.De>
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Hello,
finally I succeeded in compiling the xfs kernel module for Linux
2.2.10 on a Sparc Ultra 5. System is Debian 2.1 with some updates from
unstable. Arlad seems to run ok (arlad -t).
Now, after mounting arla on /afs I get the following:
<0> iterator(ROOT) %ls -l /
total 49
?--------- 1 root root 0 Jan 1 1970 afs
drwxr-xr-x 2 root root 1024 Jul 27 16:52 bin/
After unmounting /afs as a directory is back again:
<0> iterator(ROOT) %ll /
total 50
drwxr-xr-x 2 root root 1024 Aug 2 16:54 afs/
Any hints ?
The xfs kernel module was compiled with the following compiler/flags
(same as used for the minix kernel module):
sparc64-linux-gcc -c -DHAVE_CONFIG_H -DMODULE -D__KERNEL__ -DDEBUG
-I. -I. -Wall -m64 -pipe -mno-fpu -O2 -mcpu=ultrasparc -mcmodel=medlow
-Wstrict-prototypes -ffixed-g4 -fcall-used-g5 -fcall-used-g7
-Wno-sign-compare -fomit-frame-pointer -I/usr/src/linux/include/
-I./../include -I../../include -I./../../include
-I/home/cake/krb4-0.9.9/include xfs_syscalls.c ld -m elf64_sparc -r -o
xfs.o xfs_load.o xfs_dev.o xfs_common.o xfs_vfsops.o xfs_node.o
xfs_message.o xfs_inodeops.o xfs_deb.o xfs_cache.o xfs_syscalls.o
sparc64-linux-gcc -v
Reading specs from /usr/lib/gcc-lib/sparc64-linux/egcs-2.92.11/specs
gcc version egcs-2.92.11 19980921 (gcc2 ss-980609 experimental)
The rest of the arla distribution was compiled with the flags
./configure figured out i.e.:
gcc -c -DHAVE_CONFIG_H -DSYSCONFDIR=\"/usr/arla/etc\"
-DARLACACHEDIR=\"/usr/arla/cache\"
-DARLACONFFILE=\"/usr/arla/etc/arla.conf\"
-I. -I. -I./.. -I/home/cake/arla-0.27pre4/xfs/linux -I../include
-I./../include -I./../xfs/include -I../rxdef -I./../rxkad
-I/home/cake/krb4-0.9.9/include -DDEBUG -g -Wall -DRXDEBUG bsd-subr.c
gcc -o arlad adir.o arla.o arladeb.o cmcb.o conn.o cred.o darla.o
discon_log.o dynroot.o fcache.o fprio.o inter.o kernel.o messages.o
reconnect.o volcache.o xfs.o bsd-subr.o -L../lib/bufdir -lbufdir
-L../rxdef -lrxdefclient -L../rx -lrx -L../lwp -llwp -L../lib/sl -lsl
-lreadline -lcurses -L../lib/ko -lko -L../util -lutil -L../lib/roken
-lroken -L../rxkad -lrxkad -L/home/cake/krb4-0.9.9/lib -lkrb -ldes
-L/home/cake/krb4-0.9.9/lib -lkafs -lresolv
gcc -v
Reading specs from /usr/lib/gcc-lib/sparc-linux/2.7.2.3/specs
gcc version 2.7.2.3
Is this maybe a 32/64-bit issue? Should the compiler be the same? Gcc
2.95 doesn't compile here for some reasons I wasn't able to figure out
yet. This sparc64-linux-gcc thing is AFAIK a debianism which can't
create executables. Kernel compiles without problems. I know this is
not something a developer likes to hear as a bug report, but maybe
this is a known problem with a short answer.
Thanks for your time,
Tobias
