Thanks
I add my functions to libcrypto.num at the end (32767 ,32766 ) as your
suggestions.
On Tue, Nov 27, 2018 at 5:28 PM Matthias St. Pierre <
matthias.st.pie...@ncp-e.com> wrote:
>
> Yes, that would be a good idea. Although it does not prevent merge conflicts,
> at least the ordinals
>
> don'
On Tue, Nov 27, 2018 at 04:11:06AM -0800, Claus Assmann wrote:
> I'm trying OpenSSL 1.1.1a on FreeBSD 11.2-RELEASE-p4 and got the following
> crash in one of my test programs (I compiled OpenSSL with -g after the
> first time this happened to get at least some debug info):
>
> #0 __je_huge_sallo
You might want to check what strerror_r gives you, rather than strerror, since
on GCC platforms that's what OpenSSL uses.
Also, OpenSSL builds its table of error strings at startup (or, for older
versions, when you tell it to). It's conceivable an application's NLS settings
changed between the
Yes, that would be a good idea. Although it does not prevent merge conflicts,
at least the ordinals
don't have to be renumbered every time. (That's the way we solved the problem
in our company.)
On 27.11.18 15:58, Viktor Dukhovni wrote:
On Nov 27, 2018, at 7:38 AM, Dr. Matthias St. Pierre
wr
> On Nov 27, 2018, at 7:38 AM, Dr. Matthias St. Pierre
> wrote:
>
> Short version: Just do 'make update' and the numbers will be added
> automagically.
>
> Long version: There is a script, 'util/mkdef.pl', which gets invoked by
> 'make update'. It scans the header files
> for new APIs an up
Short version: Just do 'make update' and the numbers will be added
automagically.
Long version: There is a script, 'util/mkdef.pl', which gets invoked by 'make
update'. It scans the header files
for new APIs an updates the .num files (libcrypto.num/libeay.num and
libssl.num) accordingly. For
I'm trying OpenSSL 1.1.1a on FreeBSD 11.2-RELEASE-p4 and got the following
crash in one of my test programs (I compiled OpenSSL with -g after the
first time this happened to get at least some debug info):
#0 __je_huge_salloc (tsdn=, ptr=) at
extent.h:114
#1 0x00080122d01e in ifree (tsd=) at
On 27/11/2018 11:50, EYAL INBAR wrote:
Hello
I try to add API,CMP_build_KUR_req, to crypto lib and get
Error: CMP_build_KUR_req does not have a number assigned
Any suggestion?
This means you are compiling for a platform (probably Windows
or OS/2) where names exported from DLLs are assigned un
Hello
I try to add API,CMP_build_KUR_req, to crypto lib and get
Error: CMP_build_KUR_req does not have a number assigned
Any suggestion?
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
