Date: Fri, 16 May 2014 16:10:01 GMT From: Mark Millard <markmigm@gmail.com> To: gnome@FreeBSD.org Subject: Re: ports/188856: devel/py-gobject3 doesn't install on powerpc64 Message-ID: <201405161610.s4GGA1QN006520@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/188856; it has been noted by GNATS. From: Mark Millard <markmigm@gmail.com> To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/188856: devel/py-gobject3 doesn't install on powerpc64 Date: Fri, 16 May 2014 08:59:53 -0700 I got the same problem on 9.2-STABLE while trying to portmaster math/gnumeric. I found the following supporting details about the problem. First there was the cp command were the "freebsd-9.2-STABLE-powerpc" part of the file path in the copy ultimately comes from. It is from work/pygobject-3.8.1/Makefile.in involving: cp $(top_builddir)/PKG-INFO $(DESTDIR)$(pyexecdir)/$(EGG_NAME).egg-info where EGG_NAME = $(PACKAGE)-$(PACKAGE_VERSION)-py$(PYTHON_VERSION)-$(PLATFORM) and (from the configure file) PLATFORM=`$PYTHON -c "import sys; from distutils import util; sys.stdout.write(util.get_platform())"` That assignment does not agree with uname -p's "powerpc64" result as it is appearently/effectively used in pkg's file path generation for lstat. util.get_platform() is supposed to use os.uname()'s architecture (well, machine) tuple entry. Looking around I can not tell if it is always the same as platform.machine(). But in this context util.get_platform(), os.uname()[4], and platform.machine() all result in just "powerpc" (no 64). This may or may not be correct from python's definitions of intent: I'm no expert at that. I would *guess* that pkg sets the context here that py-gobject3 needs to agree with pkg's file path use for lstat. In other words: I guess that the above copy needs to change to use the file path shown in the error message: pkg-static: lstat(/usr/ports/devel/py-gobject3/work/stage/usr/local/lib/python2.7/site-packages/pygobject-3.8.1-pypython 2.7-freebsd-9.2-STABLE-powerpc64.egg-info): No such file or directory Some care is needed because EGG_NAME is also used with just ".egg" after its substitution, not just with ".egg_info" after it: There are at least 2 contexts of use. -- Mark Millard <markmigm at gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405161610.s4GGA1QN006520>