The "which package depends on which openssl ver" issue's been around a long
time.
FWIW, in general, I *never* touch openssl libs/headers in the default
distro path, /usr.
Just leave that alone -- too many distro packages (still) make (invalid)
assumptions about that being the only/preferred openss
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 wi
Ah, I guess it wanted you to also compile OpenSSL for i386 and putting
that (different!) opensslconf.h in the i386-specific directory.
That also means you should have moved opensslconf.h to the subdir, not
copied it.
On 22/10/2018 20:42, Skip Carter wrote:
Found the problem!
Thanks to Selva for
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
On Mon, 2018-10-22 at 17:52 +, Salz, Rich via openssl-users wrote:
> > Yes the macro is there, its just not being expanded by the pre-
>
> compiler.
>
> That makes no sense.
I am stumped, FYI here is the the relevant output of the precompiler
(cpp)
# 261 "/usr/include/openssl/ec.h
That's very odd. Are you *sure* the one you're looking at is the one
actually included?
Cheers,
Richard
In message <1540230631.4886.20.ca...@taygeta.com> on Mon, 22 Oct 2018 10:50:31
-0700, Skip Carter said:
> Yes the macro is there, its just not being expanded by the pre-
> compiler.
>
>
>
On Mon, Oct 22, 2018 at 1:51 PM Skip Carter 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 pi
You're surely looking in the wrong header file. The compiler
is using a different one in which the macro is NOT defined.
> On Oct 22, 2018, at 1:50 PM, Skip Carter wrote:
>
> Yes the macro is there, its just not being expanded by the pre-
> compiler.
>
>
> On Mon, 2018-10-22 at 08:55 +0100, M
>Yes the macro is there, its just not being expanded by the pre-
compiler.
That makes no sense.
Please look at your compiler manpages and figure out how to turn on verbose
compiler output. Something is strange in your environment.
--
openssl-users mailing list
To unsubscribe: ht
Yes the macro is there, its just not being expanded by the pre-
compiler.
On Mon, 2018-10-22 at 08:55 +0100, Matt Caswell wrote:
>
> On 21/10/2018 20:01, Skip Carter wrote:
>
> Does your opensslconf.h have the DEPRECATEDIN_1_2_0 macro defined in
> it?
>
> Matt
--
Skip Carter
Taygeta Scientifi
On 21/10/2018 20:01, Skip Carter wrote:
> Thats what I originally thought.
>
> I experimented with manually invoking the pre-compiler (cpp) and this
> is what I get:
>
>
> DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
>
>DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
That is "proof" that the pre-processor doesn’t have the right -I flags. Try
running with the -v option or something.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Thats what I originally thought.
I experimented with manually invoking the pre-compiler (cpp) and this
is what I get:
DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
BIGNUM *p,
>And I still have the problem with those macros.
The problem is almost definitely this: the files that you are compiling (not
openssl) are picking up the wrong header files from openssl.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On Sun, 2018-10-21 at 02:10 +, Blumenthal, Uri - 0553 - MITLL
wrote:
> On 10/20/2018, 21:41, "openssl-users on behalf of Skip Carter" sl-users-boun...@openssl.org on behalf of s...@taygeta.com> wrote:
> Yes, that works just fine for me too. But if I include ssl.h I
> have
> the probl
On 10/20/2018, 21:41, "openssl-users on behalf of Skip Carter"
wrote:
Yes, that works just fine for me too. But if I include ssl.h I have
the problem. The various DEPRECATED.. macros don't get pre-compiled
and get handed to the compiler. I think I improperly installed the
heade
You probably do not have the headers installed into the right include path.
You should do "make install" and not cp things by hand, as you'll need the
headers and the libraries, etc.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Uri,
Yes, that works just fine for me too. But if I include ssl.h I have
the problem. The various DEPRECATED.. macros don't get pre-compiled
and get handed to the compiler. I think I improperly installed the
headers.
On Sun, 2018-10-21 at 00:36 +, Blumenthal, Uri - 0553 - MITLL
wrote:
> I'
I'm not sure I understand what you're doing, but:
$ cat ttt.c
#include
#include
int main(void)
{
printf("OPENSSL_VERSION_NUMBER %lx\n",OPENSSL_VERSION_NUMBER);
return 0;
}
$ gcc -o ttt ttt.c -lcrypto
$ ./ttt
OPENSSL_VERSION_NUMBER 1000210f
$ gcc -o ttt -I$HOME/openssl-1.1/include ttt.c -L$H
All,
I am thinking that the DEPRECATED... macros are not expanded by the
pre-parser so the compiler sees them as a weirdly formed function and
doesn't like it.
I "installed" the header files with 'cp' was there a make command that
I was supposed to use ?
On Fri, 2018-10-19 at 16:54 -0700, Skip
On Fri, 2018-10-19 at 22:54 +0100, Matt Caswell wrote:
>
>
> It looks like its not picking up the definition of the
> DEPRECATEDIN_1_2_0 macro for some reason.
>
> That macro should be defined in opensslconf.h (which is included from
> ec.h), and looks like this:
>
> /*
> * Do not deprecate th
On 19/10/2018 20:03, Skip Carter wrote:
> Hello all,
>
> I recently installed from source, openssl-1.1.1 on a Debian box (like
> most distributions the Debian version is quite old and my application
> needs very recent libraries). It built and installed without warnings
> or errors (Thanks to a
Hello all,
I recently installed from source, openssl-1.1.1 on a Debian box (like
most distributions the Debian version is quite old and my application
needs very recent libraries). It built and installed without warnings
or errors (Thanks to all concerned in creating software that can do
that).
23 matches
Mail list logo
