Jump to content
The Dark Mod Forums

WXU 3.0.5 not found with the latest version of wxgtk 3.0


Recommended Posts

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recent Status Updates

    • Ansome

      Finally got my PC back from the shop after my SSD got corrupted a week ago and damaged my motherboard. Scary stuff, but thank goodness it happened right after two months of FM development instead of wiping all my work before I could release it. New SSD, repaired Motherboard and BIOS, and we're ready to start working on my second FM with some added version control in the cloud just to be safe!
      · 0 replies
    • Petike the Taffer  »  DeTeEff

      I've updated the articles for your FMs and your author category at the wiki. Your newer nickname (DeTeEff) now comes first, and the one in parentheses is your older nickname (Fieldmedic). Just to avoid confusing people who played your FMs years ago and remember your older nickname. I've added a wiki article for your latest FM, Who Watches the Watcher?, as part of my current updating efforts. Unless I overlooked something, you have five different FMs so far.
      · 0 replies
    • Petike the Taffer

      I've finally managed to log in to The Dark Mod Wiki. I'm back in the saddle and before the holidays start in full, I'll be adding a few new FM articles and doing other updates. Written in Stone is already done.
      · 4 replies
    • nbohr1more

      TDM 15th Anniversary Contest is now active! Please declare your participation: https://forums.thedarkmod.com/index.php?/topic/22413-the-dark-mod-15th-anniversary-contest-entry-thread/
       
      · 0 replies
    • JackFarmer

      @TheUnbeholden
      You cannot receive PMs. Could you please be so kind and check your mailbox if it is full (or maybe you switched off the function)?
      · 1 reply
×
×
  • Create New...