[Openswan Users] openswan 2.4.0 build with 2.4.31

Michele Baldessari michele-lists at pupazzo.org
Fri Sep 16 00:10:14 CEST 2005


* 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.openswan.org/pipermail/users/attachments/20050915/c23b0497/attachment.bin


More information about the Users mailing list