[openssl-users] What to do with deprecation errors

[Richard Levitte]

If the compiler found opensslconf.h in
/usr/include/x86_64-linux-gnu/openssl/, that usually means you have an
distribution openssl package installed, one that other programs are
relying on.

Depending on the version of that package, you may have screwed things
up or not.  If you're lucky, things will go smoothly, but be warning
that your "installation" probably will get overwritten next time you
do an update that affects the openssl package.

For custom installations, I'd suggest using the /usr/local tree.  This
is what the default OpenSSL configuration + make install does.

Cheers,
Richard

In message <1540233767.4886.24.camel at taygeta.com> on Mon, 22 Oct 2018 11:42:47 -0700, Skip Carter <skip at taygeta.com> said:

> Found the problem!
> Thanks to Selva for pointing the way.
> 
> The compiler was looking for opensslconf.h (and only this file, not any
> other header files) at /usr/include/x86_64-linux-
> gnu/openssl/opensslconf.h  when I copied
> /usr/include/openssl/opensslconf.h to that location, everything worked.
>   The -E flag gave it away (it was buried in the cpp output too, but
> was easy to miss).
> 
> 
> On Mon, 2018-10-22 at 14:00 -0400, Selva Nair wrote:
> > On Mon, Oct 22, 2018 at 1:51 PM Skip Carter <skip at taygeta.com> wrote:
> > > 
> > > Yes the macro is there, its just not being expanded by the pre-
> > > compiler.
> > 
> > All these tests say the same thing that you are picking up a wrong
> > (old) header.
> > 
> > So do:
> > 
> > gcc -E your-program.c | grep opensslconf.h
> > 
> > Then check whether the one it picks up is the right one and has
> > the macro defined.
> > 
> > Selva
> -- 
> Skip Carter
> Taygeta Scientific Inc.
>