Arch Linux compilation/installation isn't Cooperative #1625
Labels
Comments
|
Have you ever compiled/installed a local copy of SDL2 or SDL2_net? |
|
I don't believe I have; Like I said, could very be likely the issue's on my end. |
|
Do you mean you haven't installed SDL2 and SDL2_net yet? |
|
SDL2 and SDL2_net are installed on the system, though I got them through the official repository. |
|
Something like this should work: If not, I think you'll need to do some basic troubleshooting steps, e.g. |
By this you mean the official SDL2 repository or the official Arch repository? |
Got the packages from the latter.
I think I already tried the commands you suggested, but went ahead and re-installed the packages anyhow, but alas, still didn't quite work. Here's the output of |
|
Do you have |
Yep, re-installed it and tried it again just to make sure, which unfortunately resulted in the same problem. |
|
I think this might be a problem with the current release of SDL2_net. See: libsdl-org/SDL_net#89 If you're up for it, the best way to proceed here is to try manually building and installing the library from the latest commit on the |
Well, I finally managed to manually build/install the latest SDL2-net library, but alas, I'm still met with the same error when I try compiling. Same log, same debug messages, same... same. |
|
Could you run cmake with |
|
I think you're trying to build using
|
Sure, and presuming this is supposed to replace "cmake .." during compilation and installing, this is what I got:
I am indeed using |
|
Okay, one last thing to try and then I'm out of ideas. First, navigate to the
Next we're going to try building SDL_net via autotools. Create a fresh empty Fingers crossed. |
Here's the log of the entire process, at least I think so: Still the same error when I try running :( |
|
Actually... new idea. I'm gonna try building Woof from the source, maybe that could get me somewhere. Here's to hopin'. |
|
Any news on this? Anything we can do to improve the situation from a Doom source port POV? |
Sorry for the late reply, but I did send a comment over to the package maintainer over at the AUR, but I haven't heard anything back yet. I also tried to look up the issue, but wasn't able to get anything relevant on the issue. Even with a -Syu or two, it still gives the same problem. I did try to compile it directly from source, but only ran into the same issue. |
I also use Arch, never tried the AUR package, but compiling from source works fine. Have you tried compiling other SDL projects, e.g. Chocolate/Crispy Doom? |
I did try compiling Chocolate Doom from source, and it did work. I'm gonna try compiling Woof from source again, but I'm not entirely optimistic it'll work. |
|
At first I still got the same error, but then I went over to the main directory, and ran I have no idea why. |
It seems that there are problems with the CMake configs on your system. You are probably building Chocolate Doom with |
Oh dear. Any way I can go about fixing the issue... and is this even the proper question to ask? |
|
Could you build Chocolate Doom with CMake, following the same build instruction as for Woof? |
That I did, and here's what I got: |
|
See, something's wrong on your system. What does give? It will return a list of directories separated by colons. Please check these directories for copies of |
dirs=`pkg-config --variable pc_path pkg-config | tr ':' ' '` ; for dir in $dirs ; do if test -f ${dir}/SDL2_net.pc ; then echo $dir ; cat ${dir}/SDL2_net.pc ; fi ; done |
|
|
I think I managed to figure out what's causing the build to go wrong for you. The hint is in this line of your log: You appear to have For me it works with the default But with I'd suggest removing it, for reference the
|
Well, I replaced |
|
Wow, thank you @joanbm ! |
Heh, I had someone run into similar problems with another AUR package I maintain a few years ago (albeit that package was unrelated to Woof and used autotools), so when I saw that "Check for working C compiler: /sbin/cc" I had a flash that it could be the same problem, and indeed it was. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
More or less what the title says, the package running into conflict into something with SDL2_Net. Likely might be an issue on my end, and ran into the same problem on Woof. I'm on Arch Linux, using the Linux-Zen kernel.
Here's the relevant log:
The text was updated successfully, but these errors were encountered: