WXU 3.0.5 not found with the latest version of wxgtk 3.0

[Alberto Salvia Novella]

So I'm packaging darkradiant as a pacman package. But when I execute darkradiant on the terminal it complains:

darkradiant: /usr/lib/libwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not found (required by darkradiant)

darkradiant: /usr/lib/libwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not found (required by /usr/lib/x86_64-linux-gnu/darkradiant/libwxutil-2.7.0.so)

The thing is that's the latest announced 3.0 version of wxgtk. If you install 3.1 then darkradiant complains it cannot find 3.0 at all.

Any idea why this could be? Thanks in advance.

[Alberto Salvia Novella]

Root cause is: wxgtk also tags incomplete releases, so the latest isn't offered to install.

[greebo]

Thanks, I replied in the bugtracker entry.

[Alberto Salvia Novella]

@greeboAny idea on why it fails to build when using the Debian package as source, just for my own info?

[Alberto Salvia Novella]

@greeboWell, I guess that assuming that dependent libraries will match different distros is just too optimistic.

Thanks for your assistance, and have a nice day.

[greebo]

6 hours ago, Alberto Salvia Novella said:

@greeboAny idea on why it fails to build when using the Debian package as source, just for my own info?

It's hard to tell what's wrong without seeing any error message.

I don't understand the "Debian package as source"part - there are the Git sources, and there are Debian packages which are binaries, i.e. they are already built.

[OrbWeaver]

On 4/25/2020 at 11:26 PM, Alberto Salvia Novella said:

So I'm packaging darkradiant as a pacman package. But when I execute darkradiant on the terminal it complains:

darkradiant: /usr/lib/libwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not found (required by darkradiant)

darkradiant: /usr/lib/libwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not found (required by /usr/lib/x86_64-linux-gnu/darkradiant/libwxutil-2.7.0.so)

If a binary is requesting a version symbol from a library and that symbol cannot be found, this implies that the binary was built against a different version of the library that the one it is linking with at runtime. This might occur if you have more than one version installed, or if you are building against a separate tree of development libraries that don't match the system-wide libraries used to run applications.

To be honest I don't think there should be a bugtracker entry for this, unless there is some evidence of a problem in the DarkRadiant build scripts. We don't embed any version symbols like "WXU_3.0.5" in the source code; we just ask the wx-config script to return the appropriate system-specific include and library paths. If your wx-config script is returning paths to a wxWidgets library which doesn't match the system-wide library, that is a problem with the build machine, not something we can fix at the source level.

You can see which include and library paths will be used at build time by running the wx-config script manually, e.g.

$ wx-config --libs
-L/usr/lib/x86_64-linux-gnu -pthread   -lwx_gtk2u_xrc-3.0 -lwx_gtk2u_html-3.0 -lwx_gtk2u_qa-3.0 -lwx_gtk2u_adv-3.0 -lwx_gtk2u_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0

$ wx-config --cxxflags
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread

It is quite possible that if you run these commands in your build environment they will point somewhere other than at /usr/lib/libwx_gtk3u_core-3.0.so.0, which would explain the version mismatch.

[Alberto Salvia Novella]

@OrbWeaverYeah, that's what I guessed. Thanks for the clarification.

The part that calls my attention, though, is that version 3.0.5 doesn't even exist on Debian unstable. So likely the Debian package 3.0.4 is providing 3.0.5 by mistake.

[Alberto Salvia Novella]

18 hours ago, greebo said:

there are Debian packages which are binaries

I mean that if you create a Pacman package using the Debian unstable package as binary source, running the binary leads to `WXU_3.0.5' not found.

Even when the Debian package is compiled using libwxgtk3.0-dev 3.0.4, that's the weird part.