Trouble building executor on Ubuntu 15.04 - 64 bit #3
Comments
|
I did quick test, and i386 and i686 both seem to be defined - maybe i686 needs to trigger the 486 or later code ? |
|
First, try also passing
I know the configure utility creates symlinks in a directory that point to the necessary headers, but it has been awhile since I've ran the configure utility. You could mess with the configuration that way. |
|
Tried |
|
Just checking, but you do have sdl-dev installed, right? Did you have -m32 specified in LDFLAGS and CFLAGS/CC? Sent from my iPad
|
|
SDL-1.2-dev is installed. I did have it set in CC, as above - just tried adding LDFLAGS and CFLAGS and it seems to do the same thing. |
|
Hi, https://stackoverflow.com/questions/23585435/cannot-call-xinitthreads I had trouble with this on 64 bit as I didn't have access to all the other needed 32 bit libs, but will keep trying. S |
|
I ran into the same problems on Lubuntu 14.04 64-bit but was able to get a working Executor build using the following steps over and above what you already figured out (assuming you've already installed all of the required packages by enabling multi-lib and apt-getting them with the First, I don't know the proper way to do it, but libSDL-1.2 and libX11 need to be made visible to the library search: cd /usr/lib/i386-linux-gnu
sudo ln -s libSDL-1.2.so.0 libSDL-1.2.so
sudo ln -s libX11.so.6 libX11.soSecond, your LIBS="-lSDL-1.2 -lX11 -ldb-5.3" |
|
I tried following ssokolow's directions, but when I try
I get configure: error: C compiler cannot create executables And when I try to build without that LIBS variable I get: I have to add I'd appreciate any assistance. |
That's a misleading error because it can mean so many things. Fundamentally, it just means that, in one of its most basic tests, " You need to find the corresponding spot in the
Could you please reformat that as a preformatted code block? As-is, it's just too much hassle to read it. (Take the original text with proper line breaks and either indent it four spaces or put a sequence of three backticks on a line alone before and after it.) Also, what distro version are you trying this on and, if it's a Debian/Ubuntu/Mint-family distro, did you run (If I have time, I'll spin up a copy in VirtualBox and see if I can replicate the problem you're experiencing.) |
|
@autc04's Executor fork is better maintained. |
|
As an occasional executor since DOS, reading what's happening on autoc04s branch is great, I'll have a go at building that. |
|
I have reformatted it now, apologies. This is on OpenSUSE Tumbleweed. I have installed the various build packages that would correspond to build-essential and was able to build syn68k successfully. I will check the config.log. |
|
OK, turns out my problem was libSDL requires libpulse and that wasn't getting installed. I've now got a new problem. The configure script appears to complete without errors, but running make gets me this: followed by many more of the same error. |
|
Huh. That's something I don't remember seeing. First, I'd try deleting your build folder, verifying that your checkout has no other generated files floating around, and starting over in case some stale files from your previous attempts have it confused. (I've run across projects that are fragile in that way.) (eg. A failed run might generate some files before it fails and then, when you get it working, the cached files from the first run and the differently |
|
Thanks, just tried that but the same errors occur. I had tried running make clean before running the configure and make, but I hadn't tried nuking the whole directory. Separately I've managed to get Executor2000 (the fork mentioned earlier in the thread, thanks @MaddTheSane) to build successfully. But I'm stubborn and I don't want to be defeated! Also I've learned quite a lot from this process, and I'd really like to figure out what's causing this latest issue. |
I'm trying to build on 64 bit linux - as 32 bit (I use CC= -m32 .... )
config params:
building - gets stuck as ARCH_TYPE_I386 is not delclared:
The text was updated successfully, but these errors were encountered: