[284] in arla-drinkers
Re: arla 0.12 has missing modversions.h
daemon@ATHENA.MIT.EDU (Derrick J Brashear)
Wed Sep 30 11:26:26 1998
From owner-arla-drinkers@stacken.kth.se Wed Sep 30 15:26:26 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 26320 invoked from network); 30 Sep 1998 15:26:25 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 30 Sep 1998 15:26:25 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id RAA20410
for arla-drinkers-list; Wed, 30 Sep 1998 17:21:30 +0200 (MET DST)
Received: from alycia.dementia.org (ALYCIA.DEMENTIA.ORG [128.2.35.149])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id RAA20401
for <arla-drinkers@stacken.kth.se>; Wed, 30 Sep 1998 17:21:20 +0200 (MET DST)
Received: from johnstown.andrew.cmu.edu (JOHNSTOWN.ANDREW.CMU.EDU [128.2.35.156]) by alycia.dementia.org (8.8.5/8.8.7) with SMTP id LAA01346 for <arla-drinkers@stacken.kth.se>; Wed, 30 Sep 1998 11:21:10 -0400 (EDT)
Date: Wed, 30 Sep 1998 11:21:16 -0400 (EDT)
From: Derrick J Brashear <shadow@dementia.org>
Reply-To: Derrick J Brashear <shadow@dementia.org>
Subject: Re: arla 0.12 has missing modversions.h
cc: arla-drinkers@stacken.kth.se
In-Reply-To: <lv1d88dfx76.fsf@yakko.stacken.kth.se>
Message-ID: <ML-1.3.2.907168876.113.shadow@johnstown.andrew.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
> > Hmmm... I thought I made myself rather clear, but I'll try it
> > again differently. You had said that the current version of arla (0.12)
> > works under Slackware (along with libc5 and 2.0 kernels). It doesn't,
> > at least in my case, it has a problem with unresolved symbols when
> > loading the xfs module. I included linux/modversions.h as Alex
> > suggested and the problem went away. Any questions?
>
> In the Slackware setup that I have tested arla on, linux/modversions.h
> does not exist, which makes it an error to include it.
>
> Please note that there are a lot of degrees of liberty involved, and I
> would like a solution that works on all systems, but every patch that
> has been sent to me has failed to work on some platforms. If you have
> a patch that works everywhere, I'd be glad to incorporate it.
Does linux/modversions.h work everywhere it exists? Or rather, if it exists and
including it causes a failure, what's the failure? I'm not saying it doesn't
cause a failure when you include it, I'm just trying to gather information.
-D