 |
The linker error indeed refers to a missing Python symbol which is defined in the corresponding import library, which you've been adding by "-lpython3.5m". Though I'm not sure what I can do at this point to resolve this. Am I supposed to update the makefiles such that they work in both Debian-based distros and Arch? Is that something that can be done at all? |
 |
i honestly wouldn't know. perhaps './configure' doesn't get it exactly right, in all cases ? feel free to close again. sorry. |
|
|
I'm not an automake expert by all standards, so I'd be grateful if someone with actual knowledge about this problem could give me some advice. I'm also not sure how to even try compilation in Arch, there doesn't seem to be a fully configured live ISO to start or even install it. Do they seriously require all of their users to start from scratch? |
|
|
Can you show me the output of this command on your system? python2-config --libs |
|
|
Ah, nevermind, it's in the config.log you attached. It shows that your python linker command line is "-lpython2.7 -lpthread -ldl -lutil -lm", which is Python 2.7. But the boost python library seems to refer to Python 3: BOOST_PYTHON_LIBS='-lboost_python3' Can you check which boost python package you have installed? |
|
|
yes, arch linux expects you to start from scratch; its sort of the point of arch linux. having said that, there currently is an .iso booted text/console based installer available here : https://arch-anywhere.org/ $ python2-config --libs -lpython2.7 -lpthread -ldl -lutil -lm $ python3-config --libs -lpython3.5m -lpthread -ldl -lutil -lm $ python-config --libs -lpython3.5m -lpthread -ldl -lutil -lm not sure about the 'boost python' package you requested; there doesn't seem to be a specific 'boost python' package (although I may have gotten the command wrong). $ pacman -Ss boost extra/boost 1.62.0-4 [installed] Free peer-reviewed portable C++ source libraries - development headers extra/boost-libs 1.62.0-4 [installed] Free peer-reviewed portable C++ source libraries - runtime libraries python3 does seem to be the default, though, with python2 installed as an extra: $ python --version Python 3.5.2 $ python2 --version Python 2.7.13 or perhaps it's part of the 'python' package ? https://www.archlinux.org/packages/extra/i686/boost/ which states : python (optional) - for python bindings python2 (optional) - for python2 bindings |
|
|
it looks like all the 'boost_python' libs are part of the 'boost' or 'boost-libs' package: $ find / -name \*boost_python\* -exec pacman -Qo {} \; 2>/dev/null /usr/lib/libboost_python3.so is owned by boost-libs 1.62.0-4 /usr/lib/libboost_python.a is owned by boost 1.62.0-4 /usr/lib/libboost_python.so is owned by boost-libs 1.62.0-4 /usr/lib/libboost_python.so.1.62.0 is owned by boost-libs 1.62.0-4 /usr/lib/libboost_python3.so.1.62.0 is owned by boost-libs 1.62.0-4 /usr/lib/libboost_python3.a is owned by boost 1.62.0-4 |
|
|
Yes, ok, I see the boost-libs package is the only one you need on your system. It contains both the libboost-python and liboost-python3 libraries. DarkRadiant's configure.ac file refers to "python2-config" (hardcoded), which is a problem, since the boost.m4 macro seems to pick libboost-python3. I guess it just picks the more recent Python version when in doubt, using the generic "python-config" command. Can you try to change the line 139 in configure.ac to use python-config instead of python2-config? This should make it work on your system again. I'm not sure though what to do about other distros. I'm mainly focused on getting it to compile in Ubuntu. (What I definitely don't have time to do is to build linux systems from the command line, I mean, come on, it's almost 2017 now?) |
|
|
I checked the history of DR's configure.ac file, and it appears that it was set up to use python-config in the past. In 2014 I applied a patch to configure.ac by the user ezze, which changed it to python2-config (incidentally, the user was running Arch too). I'll run a quick check in Ubuntu, but I'm inclined now to change it back, since the boost.m4 macro also uses python-config and using something different is just bound to produce problems. |
|
|
thanks ! yes, changing "python2-config" into "python-config" at line 139 in 'configure.ac' (and running git pull, ./autogen.sh, ./configure, of course) solves the issue. And yes, 'stuff' is still done from the command line, even in almost-2017. remember: 'in the beginning... was the command line' ;) but if you dont like the 'arch linux' approach, you are going to be horrified by 'linux from scratch' (http://www.linuxfromscratch.org/) ;) |
|
|
Glad it's working for you, I'll change it back after testing it in Ubuntu 14.04. I found the thread from 2014: http://forums.thedarkmod.com/topic/15767-darkradiant-archlinux The problems arose when the boost.m4 macro (which was also modified in that same patch) was replaced with a newer version. The change to python2-config is not a good idea, after all. And yes, I've heard of Linux from Scratch. Not that I'm uncapable of doing stuff in the command line. I've compiled Linux from source code that came on 20 floppy disks back in 1993 or something, but over the years I've lost interest in doing so much groundwork just because I can, even if I had the time for that these days. |
|
|
thanks ! good to verify it works out in other linux distro's, too. and sorry this has gone so far off topic, but: to me personally, things like 'linux from scratch' are a good way to learn what goes on 'under the hood', but once you've done it (unless of course you are the maintaining a linux distro yourself), take the knowledge so you can effectively troubleshoot when things go wrong, but on a day-to-day-basis automate the heck out of it as much as you possibly can, so it all can run reproducibly on auto-pilot. ;) |
|
|
Fixed in 794104b4ff13cdc2186ab57285983113ed3ba340 Thanks for the assistance, mhoes |
- Anonymous
