FS#52735 - wxPython needs rebuild after wxGTK update

Attached to Project: Arch Linux
Opened by Kyle (2bluesc) - Friday, 27 January 2017, 20:07 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 26 July 2017, 15:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
It appears that wxpython rebuild is needed following the wxgtk update. Opening an application such as kicad's pcbnew which uses wxpython generates a warning:

> Mismatch between the program and library build versions detected.
> The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx containers,compatible with 2.8),
> and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8).


Additional info:
* wxpython-3.0.2.0-2
* wxgtk-3.0.2-6
* kicad 4.0.5-2


Steps to reproduce:
1. Update to latest packages
2. Open kicad pcbnew
3. Warning will pop-up

To resolve the issue, I rebuilt wxgtk-3.0.2-6 and re-installed it. Warning went away.

I assume other packages are also affected by this but may not be checking.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 26 July 2017, 15:08 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 27 January 2017, 23:50 GMT
Guess you mean rebuilding wxpython instead?

wxgtk was recompiled recently using gcc 6.3, wxpython was packaged in 2015 using gcc 5.2 or 5.3. That's where the C++ ABI mismatch comes from.
Comment by Kyle (2bluesc) - Saturday, 28 January 2017, 02:39 GMT
Yes, sorry, I meant that I rebuilt wxpython.
Comment by Jan de Groot (JGC) - Friday, 10 March 2017, 14:53 GMT
Reopening: this warning is thrown in your face everytime you use something wxpython-related in kicad. If it was a simple console warning we could just ignore it, but having to click a popup everytime is annoying and should be fixed.

As for the last two reopen requests: yes we patch the error back to warning, as the ABI mismatch isn't fatal in most cases. We don't want to rebuild all wxgtk applications on a gcc update.
Comment by John Beard (jjbeard) - Friday, 10 March 2017, 15:41 GMT
Hi Jan, sorry about the double re-open request, I reloaded the page after the request vanished as I thought it was an old tab and resent form data without thinking.

I understand why the patch is there as a fatal error would just break everything except in perfect-lockstep update. I was thinking of a different wx logging level that goes right to console, but debug and verbose don't do anything in non-debug builds, so I'm not sure.
Comment by Kyle Bradfield (walmartshopper) - Thursday, 23 March 2017, 18:44 GMT
Displaycal is also affected by this.
Comment by John Beard (jjbeard) - Tuesday, 11 April 2017, 01:54 GMT
This is a modification to the wxgtk patch to sends the warning to the console rather than pop a dialog. This is done by temporarily redirecting logging output.

This should then avoid this problem for all wx libraries (not just wxPython).
   make-abicheck-non-fatal.patch (0.9 KiB)

Loading...