Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade

On Sun, 20 May 2007 13:44:13 +0200
Ed Schouten <ed_at_fxq.nl> wrote:

> * Vlad GALU <dudu_at_dudu.ro> wrote:
> >  On 5/20/07, Ed Schouten <ed_at_fxq.nl> wrote:
> > > Hello,
> > >
> > > * Vlad GALU <dudu_at_dudu.ro> wrote:
> > > >    There might be a PEBKAC here, but after applying the patch
> > > >  (cleanly) and rebuilding/reinstalling everything under
> > > >  /usr/src/secure, OpenVPN still crashes with SIGILL.
> > >
> > > The problem lies within macro's that are compiled within
> > > applications that make use of the OpenSSL library. Could you try
> > > recompiling OpenVPN (and other apps/libs that make use of
> > > OpenSSL) as well?
> > 
> >    Yes, I've just done that. The crashes I mentioned happen when I
> >  rebuild the OpenVPN port, while performing the sanity tests (right
> >  after compiling and linking).
> 
> Well, I guess the previous mentioned patch doesn't fix all cases. I
> still get a lot of warnings during compilation of OpenSSL after
> applying the patch that look like this:
> 
<SKIP>
> | d1_clnt.c:912
> | d1_srvr.c:845
> | s3_clnt.c:1856
> | s3_lib.c:1756
> | s3_lib.c:1937
> | s3_srvr.c:1224
> | ssl_cert.c:215

 Just out of curiosity, did you happen to notice that files which my
patch is changing are header files? You need to install them for the
patch to have any effect. Otherwise rebuilding in secure/ will happily
use unpatched header files from /usr/inlcude/openssl.

I suggest you just rebuild the whole world instead of trying to cut
corners.

-- 
Alexander Kabaev