[MacPorts] #36904: grass: add wxPython variant

MacPorts noreply at macports.org
Thu Jun 6 15:25:34 PDT 2013


#36904: grass: add wxPython variant
-----------------------------+--------------------
  Reporter:  drew.mueller@…  |      Owner:  g5pw@…
      Type:  enhancement     |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  grass           |
-----------------------------+--------------------

Comment (by vaccari@…):

 Replying to [comment:8 g5pw@…]:
 > This should be fixed in r106731. Feel free to reopen if it still doesn't
 work.

 I've removed grass, reinstalled with +wxPython and +wxWidgets


 {{{
 --->  Computing dependencies for grass
 --->  Fetching archive for grass
 --->  Attempting to fetch
 grass-6.4.2_3+wxPython+wxwidgets.darwin_12.x86_64.tbz2 from
 http://lil.fr.packages.macports.org/grass
 --->  Attempting to fetch
 grass-6.4.2_3+wxPython+wxwidgets.darwin_12.x86_64.tbz2 from
 http://mse.uk.packages.macports.org/sites/packages.macports.org/grass
 --->  Attempting to fetch
 grass-6.4.2_3+wxPython+wxwidgets.darwin_12.x86_64.tbz2 from
 http://packages.macports.org/grass
 --->  Fetching distfiles for grass
 --->  Verifying checksum(s) for grass
 --->  Extracting grass
 --->  Applying patches to grass
 --->  Configuring grass
 --->  Building grass
 --->  Staging grass into destroot
 --->  Installing grass @6.4.2_3+wxPython+wxwidgets
 --->  Deactivating grass @6.4.2_3+wxwidgets
 --->  Cleaning grass
 --->  Activating grass @6.4.2_3+wxPython+wxwidgets
 --->  Cleaning grass
 --->  Updating database of binaries: 100.0%
 --->  Scanning binaries for linking errors: 100.0%
 --->  No broken files found.
 }}}

 but still I'm getting the error when starting grass64



 {{{
 Hit RETURN to continue

 Starting GRASS ...
 ERROR: wxGUI requires wxPython. No module named wxversion
 Error in GUI startup. If necessary, please
 report this error to the GRASS developers.
 Switching to text mode now.
 Hit RETURN to continue...

 }}}

 Is there any other step that I should take? Or anything else that I could
 try that could help in tracking the problem?

 Thanks for looking into it!

-- 
Ticket URL: <https://trac.macports.org/ticket/36904#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list