gcc 3.3.1 complains about racoon/crypto_openssl.c's uses of "(unsigned char **)&p)" (3 of them). I thought there was a whole thread about this earlier... warning: dereferencing type-punned pointer will break strict-aliasing rules gcc 2.95.3 is happy. Thoughts? Cheers, Patrick