[openssl-dev] [openssl.org #4345] Bug - Cannot build openssl-1.1.0-pre4-dev on NetBSD 6_Stable

[yancm via RT]

Richard,
OpenSSL 1.1.0-pre6-dev compiled, tested and installed fine with
"no-shared" config flag
Shared mode compiled and tested fine, but openssl executable could not
find it's libraries once installed...

I suggest to close this ticket...

thanks,
gene

> Hey,
>
> would you mind trying the latest beta, or a fresh master checkout? I can't
> know
> for sure, but it's possible you'll get better results now. If not, I'm all
> ears.
>
> Cheers,
> Richard
>
>
> On Thu Feb 25 13:13:41 2016, yancm at SDF.ORG wrote:
>> The first parts of this report are the actual build bug I think I am
>> encountering, but also, at the end, I am asking for additional help with
>> enabling the crypto-mdebug and crypto-mdebug-backtrace as I am trying to
>> to diagnose a compatibility issue between tor and the openssl 1.1.0_dev
>> branch.
>>
>> config and output:
>> *****Config command and output*****
>> # ./config --unified --debug --api=1.1.0 no-shared
>> Operating system: i686-whatever-netbsd
>> Configuring for BSD-x86-elf
>> Configuring OpenSSL version 1.1.0-pre4-dev (0x0x10100004L)
>> no-crypto-mdebug [default] OPENSSL_NO_CRYPTO_MDEBUG (skip dir)
>> no-crypto-mdebug-backtrace [forced]
>> OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE (skip dir)
>> no-ec_nistp_64_gcc_128 [default] OPENSSL_NO_EC_NISTP_64_GCC_128 (skip
>> dir)
>> no-egd [default] OPENSSL_NO_EGD (skip dir)
>> no-heartbeats [default] OPENSSL_NO_HEARTBEATS (skip dir)
>> no-md2 [default] OPENSSL_NO_MD2 (skip dir)
>> no-rc5 [default] OPENSSL_NO_RC5 (skip dir)
>> no-sctp [default] OPENSSL_NO_SCTP (skip dir)
>> no-shared [option]
>> no-ssl-trace [default] OPENSSL_NO_SSL_TRACE (skip dir)
>> no-static-engine [default] OPENSSL_NO_STATIC_ENGINE (skip dir)
>> no-unit-test [default] OPENSSL_NO_UNIT_TEST (skip dir)
>> no-zlib [default]
>> no-zlib-dynamic [forced]
>> Configuring for BSD-x86-elf
>> IsMK1MF =no
>> CC =cc
>> CFLAG = -pthread -D_THREAD_SAFE -D_REENTRANT -DL_ENDIAN -Wall -O0
>> -g -DWHIRLPOOL_ASM -Wa,--noexecstack
>> DEFINES =DSO_DLFCN HAVE_DLFCN_H OPENSSL_THREADS
>> OPENSSL_NO_STATIC_ENGINE OPENSSL_PIC OPENSSL_BN_ASM_PART_WORDS
>> OPENSSL_IA32_SSE2 OPENSSL_BN_ASM_MONT OPENSSL_BN_ASM_GF2m SHA1_ASM
>> SHA256_ASM SHA512_ASM MD5_ASM RMD160_ASM AES_ASM VPAES_ASM GHASH_ASM
>> ECP_NISTZ256_ASM POLY1305_ASM OPENSSL_API_COMPAT=0x10100000L
>> LFLAG =
>> PLIB_LFLAG =
>> EX_LIBS =
>> CPUID_OBJ =x86cpuid.o
>> BN_ASM =bn-586.o co-586.o x86-mont.o x86-gf2m.o
>> EC_ASM =ecp_nistz256.o ecp_nistz256-x86.o
>> DES_ENC =des-586.o crypt586.o
>> AES_ENC =aes-586.o vpaes-x86.o aesni-x86.o
>> BF_ENC =bf-586.o
>> CAST_ENC =c_enc.o
>> RC4_ENC =rc4-586.o
>> RC5_ENC =rc5-586.o
>> MD5_OBJ_ASM =md5-586.o
>> SHA1_OBJ_ASM =sha1-586.o sha256-586.o sha512-586.o
>> RMD160_OBJ_ASM=rmd-586.o
>> CMLL_ENC =cmll-x86.o
>> MODES_OBJ =ghash-x86.o
>> PADLOCK_OBJ =e_padlock-x86.o
>> CHACHA_ENC =chacha-x86.o
>> POLY1305_OBJ =poly1305-x86.o
>> PROCESSOR =
>> RANLIB =/usr/bin/ranlib
>> ARFLAGS =
>> PERL =/usr/pkg/bin/perl
>>
>> THIRTY_TWO_BIT mode
>> BN_LLONG mode
>>
>> Configured for BSD-x86-elf.
>> ***************************************
>>
>> if I gmake at the top level, the build proceeds for a while and appears
>> to
>> exit cleanly, but if I run gmake again, I get the following message:
>> # gmake
>> gmake: *** No rule to make target
>> 'usr/include/stdio.husr/include/sys/cdefs.h', needed by 'apps/openssl'.
>> Stop.
>>
>> ***************************************
>> I have problems even if I turn off debug.
>>
>> I really want debug AND I think I need to enable crypto-mdebug and
>> crypto-mdebug-backtrace so I can determine the calling line from tor
>> that
>> is crashing in openssl. The tor dev's think they have coded for
>> compatibility with openssl 1.1.0_dev, but I cannot confirm this on my
>> builds. I built tor with debug symbols, but so far, even if I set
>> breakpoints at main() in tor, running tor in gdb appears to crash in
>> openssl somewhere but I cannot execute a backtrace to see what line in
>> tor
>> is calling the openssl function that is failing. At the moment I cannot
>> even build openssl. I've had this issue for a week or two...
>>
>>
>>
>>
>>
>>
>
>
> --
> Richard Levitte
> levitte at openssl.org
>
> --
> Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4345
> Please log in as guest with password guest if prompted
>
>



-- 
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4345
Please log in as guest with password guest if prompted