Opened 11 years ago

Closed 11 years ago

#39781 closed defect (fixed)

py27-wxpython30 @ 2.9.0.4 build failure

Reported by: ci42 Owned by: jyrkiwahlstedt
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: michaelld (Michael Dickens), mojca (Mojca Miklavec), marklivingstone (Mark Livingstone), cooljeanius (Eric Gallager), p-bro, jqm12@…, mail@…
Port: py27-wxpython30 py27-wxpython-devel

Description

After the recent update of wxWidgets30 py27-wxpython30 fails to build, see the error in the attached log file. The binary packages are broken as well. If rev-upgrade is enabled the package rebuild fails with the same error.

Attachments (2)

py27-wxpython30.log (139.9 KB) - added by ci42 11 years ago.
main.log (86.3 KB) - added by jqm12@… 11 years ago.

Download all attachments as: .zip

Change History (19)

Changed 11 years ago by ci42

Attachment: py27-wxpython30.log added

comment:1 Changed 11 years ago by yanokwa@…

Cc: yanokwa@… added

Cc Me!

comment:2 Changed 11 years ago by mojca (Mojca Miklavec)

It probably fails due to mismatch between wxWidgets 2.9.5 and wxPython 2.9.4.0. The error is

src/osx_cocoa/_windows_wrap.cpp:13334:50: error: too many arguments to function call, expected 2, have 3
	    result = (bool)(arg1)->SashHitTest(arg2,arg3,arg4);
	                   ~~~~~~~~~~~~~~~~~~~           ^~~~

and the third argument has recently been removed. It would probably help if wxPython 2.9.5.0 would be released soon, else some patching is definitely needed.

comment:3 Changed 11 years ago by mojca (Mojca Miklavec)

Port: py27-wxpython-devel added

comment:4 Changed 11 years ago by ci42

Has duplicate #40008.

comment:5 Changed 11 years ago by michaelld (Michael Dickens)

Since wxWidgets 2.9.5 is not compatible with wxPython 2.9.4, can someone revert the former's ports to their prior states (2.9.4) so that the latter ports are no longer broken? Then, once both are available @2.9.5 they can both be updated together? This way of doing WX things seems reasonable to me, and IIRC has worked in the distant past.

comment:6 Changed 11 years ago by michaelld (Michael Dickens)

Cc: michaelld@… added

Cc Me!

comment:7 Changed 11 years ago by larryv (Lawrence Velázquez)

Cc: mojca@… added

comment:8 Changed 11 years ago by marklivingstone (Mark Livingstone)

Cc: livingstonemark@… added

Cc Me!

comment:9 Changed 11 years ago by mojca (Mojca Miklavec)

It's easy to revert wxWidgets back to 2.9.4, but I would be a lot more grateful for feedback on the following ports

  • graphics/wxPython-3.0
  • python/py-wxpython-3.0
  • sysutils/wxWidgets_select

from users/mojca/wxports. Plus the only two dependencies:

  • py-winpdb
  • py-robotframework-ride (I was told that there are problems with 2.9 anyway)

(Please deactivate wxWidgets/wxWidgets30/wxWidgets-devel before trying it out.)

A longer explanation has been posted on the mailing list, but I can repeat it here if needed. If these ports work, I would prefer to replace the current ports with the new ones and make wxPython independent of wxWidgets, so that upgrades of wxWidgets won't need to be delayed for the sake of wxPython.

comment:10 Changed 11 years ago by yanokwa@…

Would love to help, but how do I install these packages? 'port search wxPython-3.0' doesn't return any results.

Last edited 11 years ago by yanokwa@… (previous) (diff)

comment:11 Changed 11 years ago by mojca (Mojca Miklavec)

svn co https://svn.macports.org/repository/macports/users/mojca/wxports

and then follow instructions for setting up a local package repository

comment:12 Changed 11 years ago by yanokwa@…

Cc: yanokwa@… removed

Cc Me!

comment:13 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:14 Changed 11 years ago by p-bro

Cc: p.bro@… added

Cc Me!

comment:15 Changed 11 years ago by jqm12@…

Cc: jqm12@… added

Cc Me!

Changed 11 years ago by jqm12@…

Attachment: main.log added

comment:16 Changed 11 years ago by mail@…

Cc: mail@… added

Cc Me!

comment:17 Changed 11 years ago by mojca (Mojca Miklavec)

Resolution: fixed
Status: newclosed

This should be fixed in r110279.

Note: See TracTickets for help on using tickets.