[Openswan Users] openswan 2.4.0 build with 2.4.31

[Paul Wouters]

On Thu, 15 Sep 2005, Michele Baldessari wrote:

Okay. There was a 2.4.1 released, but since it had a bogus version number
inside the tar ball, i removed it from the ftp site.

Michael, can you roll a 2.4.1dr2 with the proper fix in it ?

Paul

> Date: Thu, 15 Sep 2005 23:10:14 +0200
> From: Michele Baldessari <michele-lists at pupazzo.org>
> To: users at openswan.org
> Subject: Re: [Openswan Users] openswan 2.4.0 build with 2.4.31
> 
> * Paul Wouters (paul at xelerance.com) wrote:
>> On Thu, 15 Sep 2005, Michele Baldessari wrote:
>>> * Arkadiusz Patyk (areq at areq.eu.org) wrote:
>>>> I have a problem with openswan 2.4.0 and kernel  2.4.31
>>> Happens with any 2.4.x series.
>>>
>>>> i686-pld-linux-gcc -D__KERNEL__
>>>> -I/home/areq/rpm/BUILD/linux-2.4.31/include -Wall -Wstrict-prototypes
>>>> -Wno-trigra
>>>> phs -O2 -fno-strict-aliasing -fno-common -Wno-sign-compare
>>>> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=
>>>> 2 -march=i686  -DMODULE  -nostdinc -iwithprefix include
>>>> -DKBUILD_BASENAME=dir_cap  -c -o dir_cap.o dir_cap.c
>>>> pfkey_v2.c: In function `pfkey_release':
>>>> pfkey_v2.c:824: error: `pfkey_sock_lock' undeclared (first use in this
>>>> function)
>>>> pfkey_v2.c:824: error: (Each undeclared identifier is reported only
>>>> once
>>>> pfkey_v2.c:824: error: for each function it appears in.)
>>>
>>> I stumbled into this too (2.4.0dr1 also has this). From a quick glance at
>>> the code
>>> (pfkey_sock_lock is defined only in NET_26...), completely untested,
>>> compiles fine:
>>
>> 2.4.1dr1 should address that issue.
>
> Nope, not yet. With 2.4.1dr1 pfkey_sock_lock is still only declared with
> NET_26 and it gets unconditionally used at pfkey_v2.c line 824 and 855.
> So it chokes on kernels 2.4 where NET_26 is not defined.
>
> thanks for looking into this.
>
> ciao,
> Michele
>

-- 

"Happiness is never grand"

 	--- Mustapha Mond, World Controller (Brave New World)