Jump to content
The Dark Mod Forums

Recommended Posts

Posted (edited)

I upgraded from openSUSE 13.2 to openSUSE Tumbleweed today. Darkradiant has apparently stopped compiling, and I get the following error during ./configure:

configure: error: invalid value: boost_major_version=

I checked my packages and should have all boost libraries installed. My boost version is 1.58.0. Any thoughts?

Edited by MirceaKitsune
Posted

I googled this issue today. Apparently the problem lies on DarkRadiant's side, and the autogen / configure script might need some tweaking. I tried a fix of my own as follows:

 

In mp/boost.m4, I commented out lines 217 and 422, which are both errors that were encountered by ./configure. They are:

AC_MSG_ERROR([invalid value: boost_major_version=$boost_major_version])

AC_MSG_ERROR([cannot find the flags to link with Boost $1])

Configuration succeeded afterwards. I was able to compile Darkradiant for well over 15 minutes, until it eventually failed with the following error:

  CXXLD    darkradiant
/usr/lib64/gcc/x86_64-suse-linux/5/../../../../x86_64-suse-linux/bin/ld: cannot find -lboost_filesystem-d
collect2: error: ld returned 1 exit status
Makefile:2043: recipe for target 'darkradiant' failed
make[1]: *** [darkradiant] Error 1

Obviously I have libboost_filesystem installed, adding the file /usr/lib64/libboost_filesystem.so.1.58.0. The setup simply fails to see them apparently.

Posted

I have the same problem!

 

./configure throws this error:
configure: error: invalid value: boost_major_version=

I have installed boost 1.58.0-3

My OS is Arch Linux.

  • 2 months later...
Posted (edited)

I have Arch Linux and use boost 1.59. To bypass this bug until it gets fixed, I opened the configure script and simply changed the line to boost_major_version=159.

-    boost_major_version=`echo "$boost_cv_lib_version" | sed 's/_//;s/_.*//'`
+    boost_major_version=159

Also, I had to change the AUTOMAKE and ACLOCAL variables in the generated makefile, because they were set to aclocal-1.14 and automake-1.14 even though I have version 1.15 on my system. WTF? Maybe the DarkRadiant devs should consider using CMake.

Edited by Radegast
  • 11 months later...
Posted

I know it's a long time since the thread has been started, but is this still an issue on your systems?

 

The automake problems typically go away if ./autogen.sh is invoked before compiling. It works for me regardless of the automake versions, be it 1.14 or 1.15.

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

    • JackFarmer

      "The Year of the Rat." 
      😄

      Al Stewart must be proud of you!
      Happy testing!
      @MirceaKitsune
      · 1 reply
    • datiswous

      I posted about it before, but I think the default tdm logo video looks outdated. For a (i.m.o.) better looking version, you can download the pk4 attached to this post and plonk it in your tdm root folder. Every mission that starts with the tdm logo then starts with the better looking one. Try for example mission COS1 Pearls and Swine.
      tdm_logo_video.pk4
      · 2 replies
    • JackFarmer

      Kill the bots! (see the "Who is online" bar)
      · 3 replies
    • STiFU

      I finished DOOM - The Dark Ages the other day. It is a decent shooter, but not as great as its predecessors, especially because of the soundtrack.
      · 5 replies
    • JackFarmer

      What do you know about a 40 degree day?
      @demagogue
      · 4 replies
×
×
  • Create New...