From owner-freebsd-threads@freebsd.org Wed Aug 2 04:46:48 2017 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96148DC5BC2 for ; Wed, 2 Aug 2017 04:46:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8400575371 for ; Wed, 2 Aug 2017 04:46:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v724km5W013681 for ; Wed, 2 Aug 2017 04:46:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 221167] pthreads unstable after botched upgrade Date: Wed, 02 Aug 2017 04:46:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: threads X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2017 04:46:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221167 Bug ID: 221167 Summary: pthreads unstable after botched upgrade Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: threads Assignee: freebsd-threads@FreeBSD.org Reporter: doctor@doctor.nl2k.ab.ca All right 1) Up to 28 July 2017 I was able to compile a openssl 1.0.2 mightly relea= se with FIPS. On 29 July , I get f [ -n "libcrypto.so.1.0.0 libssl.so.1.0.0" ]; then (cd ..; make libcrypto.so.1.0.0); fi [ -z "libcrypto" ] || /usr/local/bin/clang40 -fPIC -DOPENSSL_PIC -DZLIB_SHA= RED -DZLIB -DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -O3 -Wall -DOPENSSL_EXPERIMENTAL_JPAKE -DOPENSSL_EXPERIMENTAL_STORE -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -I/usr/local/ssl/fips-2.0/incl= ude -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_= ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -Iinclude=20 -DFINGERPRINT_PREMAIN_DSO_LOAD -o fips_premain_dso=20=20 /usr/local/ssl/fips-2.0/lib/fips_premain.c /usr/local/ssl/fips-2.0/lib/fipscanister.o libcrypto.a=20 /usr/lib/libpthread.so: undefined reference to `__sys_clock_nanosleep at FBSDprivate_1.0' /usr/lib/libpthread.so: undefined reference to `__sys_fdatasync at FBSDprivate_1.0' clang-4.0: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[2]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729 *** Error code 1 Stop. make[1]: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729/crypto *** Error code 1 Stop. make: stopped in /usr/source/openssl-1.0.2-stable-SNAP-20170729 Huh?? 2) Updating dns/bind911 with threads checking for fseeko... yes checking for static inline breakage... no checking for size_t... (cached) yes checking for ssize_t... (cached) yes checking for uintptr_t... (cached) yes checking for socklen_t... (cached) yes checking whether time.h and sys/time.h may both be included... yes checking for long long... yes checking for uname... yes checking for GCC noreturn attribute... yes checking for struct lifconf... no checking for kqueue... yes checking epoll support... no checking sys/devpoll.h usability... no checking sys/devpoll.h presence... no checking for sys/devpoll.h... no checking devpoll.h usability... no checking devpoll.h presence... no checking for devpoll.h... no checking if unistd.h or sys/types.h defines fd_set... yes checking whether byte ordering is bigendian... no checking GeoIP.h usability... yes checking GeoIP.h presence... yes checking for GeoIP.h... yes checking for library containing GeoIP_id_by_addr_gl... -lGeoIP checking for library containing fabsf... -lm checking for GeoIP support... yes checking for GeoIP Country IPv6 support... yes checking for GeoIP City IPv6 support... yes checking for GSSAPI library... disabled checking for random device... using "/dev/random" checking for arc4random... (cached) yes checking for arc4random_stir... yes checking for arc4random_addrandom... yes checking whether to build with thread support... yes checking for gcc -pthread support... no checking for pthread_create in -lpthread... no checking for thread_create in -lthr... no checking for pthread_create in -lc_r... no checking for pthread_create in -lc... no configure: error: "could not find thread libraries" =3D=3D=3D> Script "configure" failed unexpectedly. Please report the problem to mat at FreeBSD.org [maintainer] and attach the "/usr/ports/dns/bind911/work/bind-9.11.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make[1]: stopped in /usr/ports/dns/bind911 *** Error code 1 Stop. make: stopped in /usr/ports/dns/bind911 All right yet on my other server running a similar hardware configuration no errors. What gives? Also, the FreBSD 11.0 -> 11.1 did not go as smoothly as expected. --=20 You are receiving this mail because: You are the assignee for the bug.=