py27_wxpython

[Ulrich Wienands]

To Jyrki: a hardware upgrade is not in the budget, even at refurb or
used prices. I am doing this on a last-generation 17" PowerBook G4...
nothing smaller will do.

I tried installing py-wxpython instead of py27-wxpython: it bombs not
knowing what "subport" means. Now you mention that things like subport
are new... so my >Macports< system maybe too old? I did not dare
trying to update that one for fear of losing the whole thing since I
was under the firm impression that Macport 2.0.3 does not work on
Tiger. That is why I synced rather than updated (a while back in this
thread). Ryan however says: it does work under Tiger, so I guess
that'll be my next attempt, then. I could upgrade to Leo but kind-of
don't want to.

Thanks, and wish me luck...

Uli


2012/2/19, Ryan Schmidt <ryandesign at macports.org>:
>
> On Feb 19, 2012, at 08:40, Wahlstedt Jyrki wrote:
>
>> On 18.2.2012, at 22.38, Ulrich Wienands wrote:
>>
>>> Ok, so I did my sudo port -d sync. It works & updates a whole bunch of
>>> stuff.
>>>
>>> Retry to install py27-wxpython, but now... it is no longer there:
>>> --------------------
>>> [UBC-PowerBook:~] uli% sudo port -d install py27-wxpython
>>> Error: Port py27-wxpython not found
>>> To report a bug, see <http://guide.macports.org/#project.tickets>
>>> --------------------
>> So,
>> what version of MacPorts do you have? Currently the wxpython port is a
>> unified python port:
>> ===
>> jwa at bach:wine-devel> port info py27-wxpython
>> py27-wxpython @2.8.12.1 (python, graphics)
>> Sub-ports:            py24-wxpython, py25-wxpython, py27-wxpython
>>
>> Description:          wxPython is a GUI toolkit for the Python programming
>>                      language. It allows Python programmers to create
>> programs
>>                      with a robust, highly functional graphical user
>> interface,
>>                      simply and easily. It is implemented as a Python
>> extension
>>                      module (native code) that wraps the popular wxWindows
>>                      cross platform GUI library, which is written in C++.
>> Homepage:             http://www.wxpython.org/
>>
>> Library Dependencies: python27, wxWidgets
>> Platforms:            darwin
>> License:              unknown
>> Maintainers:          jwa at macports.org
>> ===
>> So, if you have a port py-wxpython containing string 'subport' in it
>> ('port cat py-wxpython'), you should have a MacPorts-version that supports
>> the feature. I must confess that I can't say immediately, which version
>> introduced this.
>
> Right, subports is a recent MacPorts feature. I already told him to upgrade
> to the latest MacPorts by using "sudo port selfupdate".
>
>>
>>> Sure enough; the sync deleted py27-wxpython. It added
>>> py27-wxpython-devel, which neeeds wxWidgets-devel. Trying that one,
>>> and it bombs:
>>> ----------------------------
>>> <snipped out updating of some dependencies that worked>...
>>>
>>> DEBUG: OS darwin/8.11.0 (Mac OS X 10.4) arch powerpc
>>> DEBUG: org.macports.load registered provides 'load', a pre-existing
>>> procedure. Target override will not be provided
>>> DEBUG: org.macports.distfiles registered provides 'distfiles', a
>>> pre-existing procedure. Target override will not be provided
>>> DEBUG: Using group file
>>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl
>>> DEBUG: Reading variant descriptions from
>>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf
>>> DEBUG: universal variant already exists, so not adding the default one
>>> DEBUG: epoch: in tree: 0 installed: 0
>>> DEBUG: gperf 3.0.4_2 exists in the ports tree
>>> DEBUG: gperf 3.0.4_0  is the latest installed
>>> DEBUG: gperf 3.0.4_0  is active
>>> DEBUG: Merging existing variants '' into variants
>>> DEBUG: new fully merged portvariants:
>>> DEBUG: Changing to port directory:
>>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gperf
>>> DEBUG: OS darwin/8.11.0 (Mac OS X 10.4) arch powerpc
>>> DEBUG: org.macports.load registered provides 'load', a pre-existing
>>> procedure. Target override will not be provided
>>> DEBUG: org.macports.distfiles registered provides 'distfiles', a
>>> pre-existing procedure. Target override will not be provided
>>> DEBUG: Using group file
>>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl
>>> DEBUG: Reading variant descriptions from
>>> /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf
>>> DEBUG: invalid command name "installs_libs"
>>>   while executing
>>> "installs_libs   no"
>>>   (file "Portfile" line 12)
>>>   invoked from within
>>> "source Portfile"
>>>   invoked from within
>>> "$workername eval source Portfile"
>>>   (procedure "mportopen" line 49)
>>>   invoked from within
>>> "mportopen $porturl [array get interp_options] [array get variations]"
>>> Error: Unable to open port: invalid command name "installs_libs"
>>> DEBUG: upgrade libiconv failed
>>>   while executing
>>> "macports::_upgrade_mport_deps $mport $target"
>>>   (procedure "mportexec" line 26)
>>>   invoked from within
>>> "mportexec $workername $target"
>>> Error: Unable to execute port: upgrade libiconv failed
>>> To report a bug, see <http://guide.macports.org/#project.tickets>
>>> [UBC-PowerBook:~] uli%
>>> -----------------
>> Here
>> the problem is libiconv port. This should obviously be solved before going
>> further!
>
> Actually the problem here is the gperf port, which is a dependency of the
> libiconv port. The inability to understand the "installs_libs" directive is
> also a symtom of having a too-old version of MacPorts, which a selfupdate
> will cure.
>
>>> So now I am stuck with no more py27-wxpython and a development version
>>> what I cannot use because the wxWidgets version won't install... not a
>>> happy situation.
>>>
>>> What gives?
>>>
>> So,
>> is there any possibility for you to upgrade? PPC is supported in Leopard,
>> IIRC, though even that is an old version, and may be hard to get. Probably
>> would be better to buy new hardware, too, but I don't know your options
>> (refurbished machines should be quite ok)?!
>
> While buying a new Mac, or upgrading the old one to Leopard, might be
> beneficial, it has no bearing on the problem he's experiencing. MacPorts
> 2.0.3 continues to work fine on PPC and Tiger. Individual ports might of
> course no longer support PPC or Tiger, but there's no indication in any of
> the above that that's the case for the ports being used here.
>
>
>