On 23/04/2020 18:01, Sam Roberts wrote: > Resending to -users. > > On Thu, Apr 23, 2020 at 9:58 AM Sam Roberts <vieuxtech@xxxxxxxxx> wrote: >> >> Seems to be something wrong with the way config is generating the >> version strings: >> gcc -Icrypto -I. -Iinclude -Iproviders/common/include >> -Iproviders/implementations/include -Icrypto/include -DAES_ASM >> -DBSAES_ASM -DCMLL_ASM -DECP_NISTZ256_ASM -DGHASH_ASM -DKECCAK1600_ASM >> -DMD5_ASM -DOPENSSL_BN_ASM_GF2m -DOPENSSL_BN_ASM_MONT >> -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 >> -DPOLY1305_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DVPAES_ASM >> -DWHIRLPOOL_ASM -DX25519_ASM -fPIC -pthread -m64 -Wa,--noexecstack >> -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_BUILDING_OPENSSL >> -DOPENSSL_PIC -DOPENSSLDIR="\"/usr/local/ssl\"" >> -DENGINESDIR="\"/usr/local/lib/engines-3\"" >> -DMODULESDIR="\"/usr/local/lib/ossl-modules\"" -DNDEBUG -MMD -MF >> crypto/libcrypto-lib-cversion.d.tmp -MT >> crypto/libcrypto-lib-cversion.o -c -o crypto/libcrypto-lib-cversion.o >> crypto/cversion.c >> In file included from include/openssl/macros.h:11, >> from include/openssl/opensslconf.h:14, >> from include/openssl/macros.h:10, >> from include/openssl/crypto.h:15, >> from include/internal/cryptlib.h:23, >> from crypto/cversion.c:10: >> crypto/cversion.c: In function 'OpenSSL_version': >> include/openssl/opensslv.h:91:54: error: expected ';' before numeric constant >> 91 | # define OPENSSL_VERSION_TEXT "OpenSSL 3.0.0-alpha1 "23 Apr 2020"" >> | ^~ >> crypto/cversion.c:50:16: note: in expansion of macro 'OPENSSL_VERSION_TEXT' >> 50 | return OPENSSL_VERSION_TEXT; >> | ^~~~~~~~~~~~~~~~~~~~ >> make[1]: *** [Makefile:15616: crypto/libcrypto-lib-cversion.o] Error 1 >> make[1]: Leaving directory '/home/sam/s/openssl-3.0.0-alpha1' >> make: *** [Makefile:3009: build_sw] Error 2 >> >> >> I'm on Linux, just did a `./config; make`. >> >> Its fairly obvious what the string should have been, I edited and am >> continuing with the build. Yes - very annoying. The release scripts added the date in a commit and broke the build - then they added another commit to remove it again ready for the next release - and everything works again. So from git's point of view it worked before and it worked after...just not in the actual release!!! The workaround is straightforward (remove the quotes from the RELEASE_DATE line in the VERSION file). I've added some notes to the 3.0 release notes on the wiki about it. Matt >> >> >> On Thu, Apr 23, 2020 at 7:29 AM OpenSSL <openssl@xxxxxxxxxxx> wrote: >>> > > OpenSSL version 3.0 alpha 1 released > ==================================== > > OpenSSL - The Open Source toolkit for SSL/TLS > https://www.openssl.org/ > > OpenSSL 3.0 is currently in alpha. > > OpenSSL 3.0 alpha 1 has now been made available. > > Note: This OpenSSL pre-release has been provided for testing ONLY. > It should NOT be used for security critical purposes. > > Specific notes on upgrading to OpenSSL 3.0 from previous versions, as well > as known issues are available on the OpenSSL Wiki, here: > > https://wiki.openssl.org/index.php/OpenSSL_3.0 > > The alpha release is available for download via HTTPS and FTP from the > following master locations (you can find the various FTP mirrors under > https://www.openssl.org/source/mirror.html): > > * https://www.openssl.org/source/ > * ftp://ftp.openssl.org/source/ > > The distribution file name is: > > o openssl-3.0.0-alpha1.tar.gz > Size: 9530120 > SHA1 checksum: 4db145d3d9c9d7bfaa7b2a1fe1670f7a3781bb06 > SHA256 checksum: 9d5be9122194ad1d649254de5e72afd329252f134791389d0cef627b18ed9a57 > > The checksums were calculated using the following commands: > > openssl sha1 openssl-3.0.0-alpha1.tar.gz > openssl sha256 openssl-3.0.0-alpha1.tar.gz > > Please download and check this $LABEL release as soon as possible. > To report a bug, open an issue on GitHub: > > https://github.com/openssl/openssl/issues > > Please check the release notes and mailing lists to avoid duplicate > reports of known issues. (Of course, the source is also available > on GitHub.) > > Yours, > > The OpenSSL Project Team. > >
