Dear Russ,

I believe that you are correct. It seems that it believes that it uses
2.4kernel.
I uploaded the files at:
http://www.cs.cmu.edu/~ipandis/linux/openafs/

Regards,
-Ippokratis.


On 4/15/07, Russ Allbery <[EMAIL PROTECTED]> wrote:

Ippokratis Pandis <[EMAIL PROTECTED]> writes:

> Package: openafs-modules-source
> Version: 1.4.2-6
> Severity: important
> Justification: fails to build from source

> In my ia64 machine I installed etch stable and then tried to install
> openafs client. Unfortunately, openafs-modules-source fails to
> build. There are two problems one minor and one major.

> The first (and minor) problem is that it tries to use an invalid flag
> (-mb-step). The error message is the following:

> ---
> cc1: error: unrecognized command line option "-mb-step"
> make[5]: *** [afs_atomlist.o] Error 1
> ---

> And then the second (and major) problem appears:

> ---
> In file included from
/usr/src/modules/openafs/src/util/afs_atomlist.c:11:
> /usr/src/modules/openafs/include/afs/param.h:63:31:
> linux/modversions.h: No such file or directory
> ---

> I had the same problem when I was using sarge and reported it
> (Bug#411818).  I am reporting it as a new bug since now I am using Etch.

Both of these problems indicate that you're trying to build a 2.4 kernel
module against a 2.6 kernel.  You never did reply to my last message on
the previous bug, but now that I look at it again, the problem is fairly
clear.

So, the question is why it thinks you have a 2.4 kernel when clearly you
don't.

Could you send a complete copy of your build log for the kernel module?  I
need to see everything starting from exactly what configure parameters
were passed through all of the compiler lines.

Thank you!

--
Russ Allbery ([EMAIL PROTECTED])               <http://www.eyrie.org/~eagle/>




--
-------------------------------------------------------
Ippokratis Pandis
Ph.D. candidate
Carnegie Mellon University
Phone: +1 412 877 5134
Email: [EMAIL PROTECTED]
http://www.cs.cmu.edu/~ipandis/
-------------------------------------------------------

Reply via email to