[OpenAFS] SuSE 10.1 kernel 184.108.40.206-4/64Bit compile error -
Tue, 11 Jul 2006 19:48:42 -0400
On Monday, July 10, 2006 02:08:14 PM -0700 ted creedon
> Is there any particular branch for 64 bit?
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Derek Atkins
> Sent: Monday, July 10, 2006 11:34 AM
> To: firstname.lastname@example.org
> Cc: email@example.com
> Subject: Re: [OpenAFS] SuSE 10.1 kernel 220.127.116.11-4/64Bit compile error -
> OpenAFS 1.5.2
> "ted creedon" <firstname.lastname@example.org> writes:
>> I'm not at all sure what this error is when building OpenAFS 1.5.2.
>> Any clues?
>> /data/openafs-1.5.2/src/afs/LINUX/osi_machdep.h:55:2: error: #error Not
>> what to do about rlim (should be in the Linux task struct
> This has been discussed on the -devel list a number of times.
> The kernel tests don't work for certain bleeding-edge kernels.
It's true that for bleeding-edge kernels, sometimes there's something new
that we need to test for. However, OpenAFS does build on 2.6.16 kernels,
and a failure in the rlim test almost always means you've done something
wrong which prevents _any_ of the compile-time kernel tests from compiling.
It constantly amazes me that whenever anyone reports this, the first
response of people on this list who really ought to know better is to try
to figure out what has changed in the kernel.
Instead, the _first_ things you should be looking for are
- is configure using the same compiler that was used for your kernel?
- do you have the linux kernel headers installed, and in the right place?
- if so _why_ did configure fail to compile the tests?
Look in config.log, find the first occurrance of the string "rlim", and
look at the compiler errors around there. Not the messages from the
configure script, and not the test program that failed. What you're
interested in is the compiler errors.