Bug 1318171
Summary: | wxGTK3: Request for Rebuild to fix C++ ABI incompatibility aborts | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marcus Müller <mmueller> |
Component: | wxGTK3 | Assignee: | Lubomir Rintel <lkundrak> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | alexjnewt, lkundrak, sergio, swt |
Target Milestone: | --- | Keywords: | ABIAssurance, EasyFix |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-20 15:22:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marcus Müller
2016-03-16 08:39:35 UTC
Ah. I see now the problem and why this didn't make sense to me. You're using the Gtk2 build of wxWidgets 3.0, which is a different package and apparently still aborts (rather than warns) on the ABI mismatch. Reassigning to that package. (In reply to Scott Talbert from comment #1) > Ah. I see now the problem and why this didn't make sense to me. You're > using the Gtk2 build of wxWidgets 3.0, which is a different package and > apparently still aborts (rather than warns) on the ABI mismatch. > Reassigning to that package. Ah, that explains my confusion. I believe the last build of compat-wxGTK3-gtk2 failed, so it probably needs some patching and a rebuild for rawhide as well. I think something similar is happening in wxGTK-2.8.12-19.fc23.x86_64, for example: mediainfo-gui Warning: Mismatch between the program and library build versions detected. The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1008,wx containers,compatible with 2.4,compatible with 2.6), and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,wx containers,compatible with 2.4,compatible with 2.6). (In reply to Jeremy Newton from comment #2) > (In reply to Scott Talbert from comment #1) > > Ah. I see now the problem and why this didn't make sense to me. You're > > using the Gtk2 build of wxWidgets 3.0, which is a different package and > > apparently still aborts (rather than warns) on the ABI mismatch. > > Reassigning to that package. > > Ah, that explains my confusion. I believe the last build of > compat-wxGTK3-gtk2 failed, so it probably needs some patching and a rebuild > for rawhide as well. Yes, a simple rebuild in F22 should fix this particular issue, but yes, the package needs some attention in Rawhide - probably the same patches I did in wxGTK3. Speaking of which, is there a reason we don't just build the compat-wxGTK3-gtk2 packages out of the wxGTK3 package? It seems like a bit of duplicated effort to maintain it separately. (In reply to Sergio Monteiro Basto from comment #3) > I think something similar is happening in wxGTK-2.8.12-19.fc23.x86_64, for > example: mediainfo-gui > > Warning: Mismatch between the program and library build versions detected. > The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1008,wx > containers,compatible with 2.4,compatible with 2.6), > and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,wx > containers,compatible with 2.4,compatible with 2.6). Yes, wxGTK package probably also needs to be rebuilt. You should file a separate bug for that. (In reply to Scott Talbert from comment #5) > Yes, wxGTK package probably also needs to be rebuilt. You should file a > separate bug for that. Done https://bugzilla.redhat.com/show_bug.cgi?id=1318841 Thanks , > Ah. I see now the problem and why this didn't make sense to me. You're using the Gtk2 build of wxWidgets 3.0, which is a different package and apparently still aborts (rather than warns) on the ABI mismatch. Reassigning to that package. No, I'm not. This is definitely wxGTK3, **not** compat-wxGTK3-gtk2: see a bit of ldd below: > ldd $(which kicad)| grep -i wx libwx_gtk3u_gl-3.0.so.0 => /lib64/libwx_gtk3u_gl-3.0.so.0 (0x00007f0c53f8f000) libwx_gtk3u_aui-3.0.so.0 => /lib64/libwx_gtk3u_aui-3.0.so.0 (0x00007f0c53cf4000) libwx_gtk3u_adv-3.0.so.0 => /lib64/libwx_gtk3u_adv-3.0.so.0 (0x00007f0c53903000) libwx_gtk3u_html-3.0.so.0 => /lib64/libwx_gtk3u_html-3.0.so.0 (0x00007f0c5360e000) libwx_gtk3u_core-3.0.so.0 => /lib64/libwx_gtk3u_core-3.0.so.0 (0x00007f0c52d7d000) libwx_baseu_net-3.0.so.0 => /lib64/libwx_baseu_net-3.0.so.0 (0x00007f0c52b27000) libwx_baseu-3.0.so.0 => /lib64/libwx_baseu-3.0.so.0 (0x00007f0c52675000) libwx_baseu_xml-3.0.so.0 => /lib64/libwx_baseu_xml-3.0.so.0 (0x00007f0c52463000) libwx_gtk3u_stc-3.0.so.0 => /lib64/libwx_gtk3u_stc-3.0.so.0 (0x00007f0c52019000) > ldd /lib64/libwx_gtk3u_core-3.0.so.0 | grep -i gtk libgtk-3.so.0 => /lib64/libgtk-3.so.0 (0x00007ff16424a000) Note that the point was that I was able to fix this rebuilding wxGTK3 from source, and installing that. I never had compat-wxGTK3-gtk2 installed. (In reply to Marcus Müller from comment #7) > > Ah. I see now the problem and why this didn't make sense to me. You're using the Gtk2 build of wxWidgets 3.0, which is a different package and apparently still aborts (rather than warns) on the ABI mismatch. Reassigning to that package. > > No, I'm not. This is definitely wxGTK3, **not** compat-wxGTK3-gtk2: see a > bit of ldd below: > > > ldd $(which kicad)| grep -i wx > libwx_gtk3u_gl-3.0.so.0 => /lib64/libwx_gtk3u_gl-3.0.so.0 > (0x00007f0c53f8f000) > libwx_gtk3u_aui-3.0.so.0 => /lib64/libwx_gtk3u_aui-3.0.so.0 > (0x00007f0c53cf4000) > libwx_gtk3u_adv-3.0.so.0 => /lib64/libwx_gtk3u_adv-3.0.so.0 > (0x00007f0c53903000) > libwx_gtk3u_html-3.0.so.0 => /lib64/libwx_gtk3u_html-3.0.so.0 > (0x00007f0c5360e000) > libwx_gtk3u_core-3.0.so.0 => /lib64/libwx_gtk3u_core-3.0.so.0 > (0x00007f0c52d7d000) > libwx_baseu_net-3.0.so.0 => /lib64/libwx_baseu_net-3.0.so.0 > (0x00007f0c52b27000) > libwx_baseu-3.0.so.0 => /lib64/libwx_baseu-3.0.so.0 (0x00007f0c52675000) > libwx_baseu_xml-3.0.so.0 => /lib64/libwx_baseu_xml-3.0.so.0 > (0x00007f0c52463000) > libwx_gtk3u_stc-3.0.so.0 => /lib64/libwx_gtk3u_stc-3.0.so.0 > (0x00007f0c52019000) > > > ldd /lib64/libwx_gtk3u_core-3.0.so.0 | grep -i gtk > libgtk-3.so.0 => /lib64/libgtk-3.so.0 (0x00007ff16424a000) I am still not understanding this because you reported that your program was aborting, but wxGTK3 has a patch to change the fatal error to a warning. Can you provide steps of how you are building kicad or whatever you are building against wxGTK3 and seeing the abort? > Can you provide steps of how you are building kicad or whatever you are building against wxGTK3 and seeing the abort?
Sure:
##clean slating, i.e. getting binary package from repo
$ sudo dnf remove -y wxGTK3 wxGTK3-devel
[...]
$ sudo dnf install wxGTk3-devel
[...]
$ git clone github.com:KiCad/kicad-source-mirror kicad
[...]
$ cd kicad
$ mkdir build2
$ cd build2
$ cmake ..
[...]
$ grep -i wx CMakeCache.txt|grep -i path
_filename:FILEPATH=/usr/include/wx-3.0/wx/version.h
wxWidgets_CONFIG_EXECUTABLE:FILEPATH=/usr/bin/wx-config-3.0
wxWidgets_wxrc_EXECUTABLE:FILEPATH=/usr/bin/wxrc
$ make -j10
[...]
##builds successfully
$ kicad/kicad
AAAAND it works.
Which is good for me, but means that not even I can reproduce this. Hence, I think closing this ticket would be appropriate?
|