Thanks Salz,
That investigation I will do for all the files I added, but for sure is not
that case for the API I added (EVP_PKEY_get0_TUV) since is in a "native"
openssl file (crypto/evp/p_lib.c and include/openssl/evp.h)... But OK it
could be a side effect.
Il giorno ven 14 giu 2019 alle ore 20:
If you are adding new functions to the library, you need to
1A Make sure there is a prototype in one of the existing OpenSSL
header files;
OR
1B If your prototype is in a new header file, you will have to edit
Configurations/unix-Makefile.tmpl to pick up that f
Log into a different terminal window, run top. Figure out if it's
infinitely looping, if it's getting stuck in a syscall (which sounds likely
-- if it is the case, you need to figure out why, which could be as simple
as a needed fsck or a required kernel update to address a bug), or if you
can kil
...I just tried once more and (after a make clean) I run again a make
update, but it is stopped always in the same place. No more commands in
that specific terminal.
After that opening a new terminal and run the make, of course, I get the
same error again (Error: EVP_PKEY_get0_TUV does not have a n
It's worth trying to run make update before running make.
пт, 14 июн. 2019 г., 20:13 Giovanni Fontana :
> A little bit further...with my problem in trying to build a tailored
> version of openSSL.
>
> If I do make I get at the end of building (trying to make .map file
> before the .so files )
>
>
A little bit further...with my problem in trying to build a tailored
version of openSSL.
If I do make I get at the end of building (trying to make .map file before
the .so files )
creating test/libtestutil.a
ranlib test/libtestutil.a || echo Never mind.
/usr/bin/perl util/mkdef.pl crypto linux >
In the unmodified directory:
$ make clean
$ make 2>&1 | tee /tmp/openssl-working-build.log
In the modified directory:
$ make clean
$ make 2>&1 | tee /tmp/openssl-broken-build.log
$ diff /tmp/openssl-working-build.log /tmp/openssl-broken-build.log |
${PAGER:more}
Take note of the differences in o
The unmodified version works. As I said, it's sure the issue is on what I
added, but info from the building logs is not sufficient to figure out what
is the issue there. So as result of the building I have just:
- libcrypto.a
- libssl.a
- libcrypto.map
so what is missing are the followi
Can you try building an unmodified version of the tarball, and see if it
has a problem?
-Kyle
On Sun, Jun 9, 2019, 07:31 Giovanni Fontana
wrote:
> Hello Kurt,
>
>
>- it's perl 5, version 26, subversion 1 (v5.26.1) built for
>x86_64-linux-gnu-thread-multi
>- ldd (Ubuntu GLIBC 2.27-3u
Hello Kurt,
- it's perl 5, version 26, subversion 1 (v5.26.1) built for
x86_64-linux-gnu-thread-multi
- ldd (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
I guess is something from what I added since the original OPENSSL I'm able
to build, as well as other intermediate modifications. My issue is it
On Sat, Jun 08, 2019 at 12:26:30AM +0200, Giovanni Fontana wrote:
> */usr/bin/ld:libcrypto.map:0: syntax error in VERSION scriptcollect2:
There seems to be a problem generating the libcrypto.map file for
you. What does the file look like? Which perl version are you
using? Which libc do you use?
11 matches
Mail list logo
