From owner-freebsd-gnome@FreeBSD.ORG Fri May 16 16:40:01 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.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 3BE2FFFC for ; Fri, 16 May 2014 16:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 29E2A21C7 for ; Fri, 16 May 2014 16:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s4GGe0Yx044524 for ; Fri, 16 May 2014 16:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s4GGe0AF044523; Fri, 16 May 2014 16:40:00 GMT (envelope-from gnats) Date: Fri, 16 May 2014 16:40:00 GMT Message-Id: <201405161640.s4GGe0AF044523@freefall.freebsd.org> To: gnome@FreeBSD.org From: Mark Millard Subject: Re: ports/188856: devel/py-gobject3 doesn't install on powerpc64 Reply-To: Mark Millard X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 16:40:01 -0000 The following reply was made to PR ports/188856; it has been noted by GNATS. From: Mark Millard To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/188856: devel/py-gobject3 doesn't install on powerpc64 Date: Fri, 16 May 2014 09:39:16 -0700 (This is an extension to a prior note. But this written to largely stand on its own given the original defect report. This adds the relationship to uname -m vs. -p.) For the py-gobject3 configure file's PLATFORM=`$PYTHON -c "import sys; from distutils import util; sys.stdout.write(util.get_platform())"` the result corresponds to uname -m (i.e., powerpc): the so-called "hardware plaform" in uname terminology. util.get_platform(), os.uname()[4], and platform.machine() all result in just "powerpc" (unname -m result) as stands. The result during portmaster is a "....egg-info" file name based on PLATFORM that disagrees with the later check for the file's existence. (But PLATFORM has other uses as well and some may be correct ones for all I know.) The lstat "....egg-info" file path reported as missing corresponds to uname -p (i.e., powerpc64): the so-called "machine processor architecture" in uname terminology. I do not know if the 3 python calls are returning correct results for python's intent or not. But I would expect that py-gobject3's file naming for the "....egg-info" file reported as missing should be using uname -p style text in the file name in order to fit correctly in the overall ports environment. -- Mark Millard