From owner-freebsd-arm@FreeBSD.ORG Wed Feb 26 17:09:11 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F42DE2D for ; Wed, 26 Feb 2014 17:09:11 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D3D2910C7 for ; Wed, 26 Feb 2014 17:09:10 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WIfsa-000MrT-EZ; Wed, 26 Feb 2014 14:54:36 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s1QEsWWn039656; Wed, 26 Feb 2014 07:54:32 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18Xg2vkcvRy8QI07/bVBmbK Subject: Re: apparently, disabled POSIX scheduler in snapshot images makes ports fail From: Ian Lepore To: "Christopher J. Ruwe" In-Reply-To: <20140226130357.206cf9ae@dijkstra-old.hb22.cruwe.de> References: <20140226130357.206cf9ae@dijkstra-old.hb22.cruwe.de> Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Feb 2014 07:54:32 -0700 Message-ID: <1393426472.1149.92.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 17:09:11 -0000 On Wed, 2014-02-26 at 13:03 +0100, Christopher J. Ruwe wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > I am trying to build postgresql-client for ARMv6 Raspberry Pi with > machines installed from the images provided on the official servers > and a custom image from the crochet. > > That fails because in the configure stage, the test for thread safety > fails and dumps core. > > checking thread safety of required library functions... Abort \ > trap (core dumped) > no > configure: error: thread test program failed > This platform is not thread-safe. Check the file 'config.log' \ > or compile > and run src/test/thread/thread_test for the exact reason. > Use --disable-thread-safety to disable thread safety. > ===> Script "configure" failed unexpectedly. > Please report the problem to pgsql@FreeBSD.org [maintainer] and > attach the "/usr/ports/databases/postgresql90-client/work/postgresql-9.0.15/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 > > Investigating, I found a similar problem where somebody failed to > compile postgresql ports due to disabled KPOSIX_PRIORITY_SCHEDULING > in the kernel. > > As in that situation, in the KPOSIX scheduler is disabled: > > # strings /boot/kernel/kernel | grep POSIX > nfscl_filllockowner: not F_POSIX or F_FLOCK > POSIX P1003.1B realtime extensions > The version of POSIX 1003.2 with which the system attempts to \ > comply > Version of POSIX attempting to comply to > POSIX real time signal > POSIX shared memory > > The expected "options _KPOSIX_PRIORITY_SCHEDULING" is obviously > missing, which explains the build failure. > > Yet, in stable/10, KPOSIX seems to be enabled: > > [cjr@dijkstra:/usr/src]$ grep POSIX sys/arm/conf/RPI-B > options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time \ > extensions > > Why is _KPOSIX_PRIORITY_SCHEDULING then disabled in the snapshots? Is > my thinking wrong? > > > Thanks and cheers, > - -- > Christopher Your method of grepping for the string isn't reliable. To see if posix priority scheduling is available, use: sysctl kern.features.kposix_priority_scheduling It's almost certainly going to be set to one. Then the question becomes "what is the actual abort that's happening during configure?" -- Ian