Re: slackware and fsw2.00pre8

-----BEGIN PGP SIGNED MESSAGE-----



> I have tested freeswan 2.00pre8 on Slackware 8.0 (vanilla kernel
> 2.4.20).
> Same behaviour as
> http://lists.freeswan.org/pipermail/design/2003-February/004245.html

1) The point DHR makes about Slackware having non-compliant header files is
still valid:

http://lists.freeswan.org/pipermail/design/2003-January/004208.html

However, do we want to ship 2.00 with -Wpointer-arith disabled? Although 
enabling this during development is good for ensuring we have no issues with 
code, it may cause our users more grief. 

Is there another option short of disabling this flag? A good way of catching 
these errors and recommending this workaround?

2) Slackware uses a BSD style startup script, instead of the assumed System V 
default. Can we improve our handling of this situation?

- -- 
Sam Sgro
[email protected]

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: For the matching public key, finger the Reply-To: address.

iQCVAwUBPlYR5kOSC4btEQUtAQHxSwP7BqWWJEX6sy2lJ5xObi1kMDzSv+EtLP9b
uxiJkFfMiBrSv7c00vS697t9nLtFiZSrd2atGcT70MvRS1xxwZOYL7R4nRio2a+n
p7+gjzx4TrV+5X1y4mMW6PkZFpXlxWLJK7TWBj856LyNP7POwsIThn4AHZkT3kCI
Z79JFgTu5zY=
=cZ01
-----END PGP SIGNATURE-----