Bug 1461979
| Summary: | gnuplot wxWidgets | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | D. E. Evans <sinuhe> |
| Component: | gnuplot | Assignee: | Frantisek Kluknavsky <fkluknav> |
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | sinuhe |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-11 13:59:11 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
D. E. Evans
2017-06-15 19:20:15 UTC
#761260 does not explain much. #564090 explains that we never shipped wxGTK and we do not want to introduce it in RHEL6. As far as I know, in RHEL7, we are still not shipping wxGTK. Please, correct me if I am wrong. I am sorry if this is my oversight but I am confused. Where did you get wxWidgets to build gnuplot? (In reply to Frantisek Kluknavsky from comment #2) > As far as I know, in RHEL7, we are still not shipping wxGTK. Please, correct > me if I am wrong. This is correct. The problem is why not? The spec file has a conditional, enabling this for Fedora, but not for Red Hat. > I am sorry if this is my oversight but I am confused. > Where did you get wxWidgets to build gnuplot? Essentially, I removed the spec file conditional and rebuilt the package. A misunderstanding between us. English is not my native language, I will try again and differently. When I try `ldd $(which gnuplot-wx)` on Fedora, I can see a bunch of wxwidgets-related libraries like: libwx_gtk2u_richtext-2.8.so.0 => /lib64/libwx_gtk2u_richtext-2.8.so.0 (0x00007ff353331000) libwx_gtk2u_aui-2.8.so.0 => /lib64/libwx_gtk2u_aui-2.8.so.0 (0x00007ff3530c6000) libwx_gtk2u_xrc-2.8.so.0 => /lib64/libwx_gtk2u_xrc-2.8.so.0 (0x00007ff352e1c000) ... The same experiment on rhel - those libraries are not there. When you remove the condition disabling wxwidgets on rhel, are you sure you actually get a working wx terminal? Can you please run ldd <your_build_of_gnuplot> to see which libwx* libraries are used? Where are those libraries from? This is the equivalent snippet from my build:
libwx_gtk2u_richtext-2.8.so.0 => /lib64/libwx_gtk2u_richtext-2.8.so.0 (0x00007f3650bac000)
libwx_gtk2u_aui-2.8.so.0 => /lib64/libwx_gtk2u_aui-2.8.so.0 (0x00007f365093e000)
libwx_gtk2u_xrc-2.8.so.0 => /lib64/libwx_gtk2u_xrc-2.8.so.0 (0x00007f36506a4000)
Looking closer, it appears I'm using the wxGTK packages from EPEL. Since RHEL doesn't include those libraries, I see now why the source RPM does not include it for building. I should have looked more carefully at that.
However, my point still stands: a build that is different in Fedora from EPEL causes confusion, and a disparity of development implementation. I find it odd that Fedora is using the gtk2 not gtk3 version, but I'm not familiar enough with the library's status.
Your point makes sense but as an engineer, I am not in a position to decide to start packaging wxGTK in RHEL and maintaining it forever. You need to go through proper support channels and persuade Red Hat's management with your business case. I can not help you until then. |