Skulltag server

void.pointer · 2008-10-16 03:02:05

Hi,

As you may or may not know, Skulltag is a Doom source port. I'm trying to use Skulltag to host a Doom server on my Archlinux machine. I downloaded Skulltag (For Ubuntu) off of the Skulltag website, however when I try to run the executable I get the following:

$ skulltag-server
-bash: /usr/local/bin/skulltag-server: No such file or directory

Note also that I placed the executable "skulltag-server" in /usr/local/bin. I have downloaded all of the required dependencies through pacman (With the exception of FMOD, which I manually downloaded and placed in /usr/local/lib). I'm not here to ask how to setup Skulltag, since I don't expect anyone here to know how or even care. I mainly want to know how I can tell why this executable is failing. It's saying there's no such file or directory when this is obviously not the case. I checked the log files in /var/log but I'm not seeing anything logged.

Help is greatly appreciated.

skottish · 2008-10-16 03:11:10

Are you on a 64 bit machine? This happens sometimes when your machine is 64 bit, the binary that you're trying to run is 32 bit, and you're missing sufficient 32 libraries to run it.

void.pointer · 2008-10-16 12:41:24

skottish wrote:

Are you on a 64 bit machine? This happens sometimes when your machine is 64 bit, the binary that you're trying to run is 32 bit, and you're missing sufficient 32 libraries to run it.

I believe it is 32-bit. But how can I make sure just in case?

skottish · 2008-10-16 14:16:50

I just use uname. Notice the x86_64:

[skottish@iasE ~]$ uname -a
Linux iasE 2.6.27-ARCH #1 SMP PREEMPT Sun Oct 12 14:48:42 CEST 2008 x86_64 AMD Processor model unknown AuthenticAMD GNU/Linux

Last edited by skottish (2008-10-16 14:20:21)

void.pointer · 2008-10-16 14:44:31

It doesn't really say:

$ uname -a
Linux server 2.6.27-ARCH #1 SMP PREEMPT Sun Oct 12 14:48:42 CEST 2008 x86_64 Intel(R) Celeron(R) CPU 430 @ 1.80GHz GenuineIntel GNU/Linux

It says x86_64, which doesn't really mean much to me.

Assuming the OS is x86, what can I do to figure out why this application is failing to run? In Windows, for example, you get an error dialog showing you if any shared libraries are missing that the application requires. I would expect some log somewhere or error message with this information in Archlinux.

skottish · 2008-10-16 15:26:58

What's happening is what I thought may be happening: you have a 64 bit installation and you don't have all of the 32 bit libraries needed to run this program. Some 32 bit stuff will complain about wrong ELF class, which makes figuring this out far easier. In this case you don't have such good clues. What I would do is look at the dependencies for the program, start installing their lib32 counterparts, and try launching the program again. When you a have an adequate 32 bit back end, the program will start.

void.pointer · 2008-10-16 15:30:04

skottish wrote:

What's happening is what I thought may be happening: you have a 64 bit installation and you don't have all of the 32 bit libraries needed to run this program. Some 32 bit stuff will complain about wrong ELF class, which makes figuring this out far easier. In this case you don't have such good clues. What I would do is look at the dependencies for the program, start installing their lib32 counterparts, and try launching the program again. When you a have an adequate 32 bit back end, the program will start.

How do you figure I have an x64 install? This isn't making any sense to me.

skottish · 2008-10-16 16:19:24

The x86_64 section in uname. It would read i686 if you were running 32 bit.

void.pointer · 2008-10-16 16:22:30

skottish wrote:

The x86_64 section in uname. It would read i686 if you were running 32 bit.

What does x86_64 mean though? I thought it meant x86 *or* x64, depending on what hardware you have the appropriate would be chosen. Could you explain? S***, I'm going to have to reinstall again....

Last edited by void.pointer (2008-10-16 16:27:51)

skottish · 2008-10-16 16:33:24

void.pointer wrote:

skottish wrote:
The x86_64 section in uname. It would read i686 if you were running 32 bit.
What does x86_64 mean though? I thought it meant x86 *or* x64, depending on what hardware you have the appropriate would be chosen. Could you explain?

x86_64 means 64 bit:

http://en.wikipedia.org/wiki/X86-64

This is how Arch names it too. Arch also refers to 32 bit as i686. These definitions are the same everywhere.

x86 is more of a generic term. Unfortunately people still use it quite frequently which is adding to the confusion. The history with this is long, convoluted, and it can be used to define both architectures. So, x86_64 and i686 are definite terms, x86 is a very loose term.

void.pointer · 2008-10-16 16:36:06

skottish wrote:

void.pointer wrote:
skottish wrote:
The x86_64 section in uname. It would read i686 if you were running 32 bit.
What does x86_64 mean though? I thought it meant x86 *or* x64, depending on what hardware you have the appropriate would be chosen. Could you explain?
x86_64 means 64 bit:
http://en.wikipedia.org/wiki/X86-64
This is how Arch names it too. Arch also refers to 32 bit as i686. These definitions are the same everywhere.
x86 is more of a generic term. Unfortunately people still use it quite frequently which is adding to the confusion. The history with this is long, convoluted, and it can be used to define both architectures. So, x86_64 and i686 are definite terms, x86 is a very loose term.

Crap, I'm going to have to reinstall. My processor wasn't made to support 64-bit I believe. Sigh. I **JUST** reinstalled and got everything setup, too. I blame windows for this confusion, it uses the x86 and x64 terms heavily.

Do I have to do step 1-5 again during /arch/setup? This will pretty much erase everything if I have to... Would be great if I could simply downgrade to i686 without a reinstall.

skottish · 2008-10-16 16:40:02

void.pointer wrote:

skottish wrote:
void.pointer wrote:
What does x86_64 mean though? I thought it meant x86 *or* x64, depending on what hardware you have the appropriate would be chosen. Could you explain?
x86_64 means 64 bit:
http://en.wikipedia.org/wiki/X86-64
This is how Arch names it too. Arch also refers to 32 bit as i686. These definitions are the same everywhere.
x86 is more of a generic term. Unfortunately people still use it quite frequently which is adding to the confusion. The history with this is long, convoluted, and it can be used to define both architectures. So, x86_64 and i686 are definite terms, x86 is a very loose term.
Crap, I'm going to have to reinstall. My processor wasn't made to support 64-bit I believe. Sigh. I **JUST** reinstalled and got everything setup, too. I blame windows for this confusion, it uses the x86 and x64 terms heavily.
Do I have to do step 1-5 again during /arch/setup? This will pretty much erase everything if I have to... Would be great if I could simply downgrade to i686 without a reinstall.

I've read a number of times that it's not possible to switch over from one architecture to the other. I've seen people successfully do all sorts of crazy shit since I've been here though...

void.pointer · 2008-10-16 16:41:47

skottish wrote:

void.pointer wrote:
skottish wrote:
x86_64 means 64 bit:
http://en.wikipedia.org/wiki/X86-64
This is how Arch names it too. Arch also refers to 32 bit as i686. These definitions are the same everywhere.
x86 is more of a generic term. Unfortunately people still use it quite frequently which is adding to the confusion. The history with this is long, convoluted, and it can be used to define both architectures. So, x86_64 and i686 are definite terms, x86 is a very loose term.
Crap, I'm going to have to reinstall. My processor wasn't made to support 64-bit I believe. Sigh. I **JUST** reinstalled and got everything setup, too. I blame windows for this confusion, it uses the x86 and x64 terms heavily.
Do I have to do step 1-5 again during /arch/setup? This will pretty much erase everything if I have to... Would be great if I could simply downgrade to i686 without a reinstall.
I've read a number of times that it's not possible to switch over from one architecture to the other. I've seen people successfully do all sorts of crazy shit since I've been here though...

Well I'm by no means a Linux expert, so I guess I'm going to have to reinstall again... :(:(:(:(:(:(:(:(:(:(

Thanks for the help.

void.pointer · 2008-10-16 20:05:05

Wait a minute... If my processor couldn't support x86_64, wouldn't Archlinux fail to install/work? It's been working flawlessly so far. Does that mean my processor can support 64-bit?

skottish · 2008-10-16 20:07:03

void.pointer wrote:

Wait a minute... If my processor couldn't support x86_64, wouldn't Archlinux fail to install/work? It's been working flawlessly so far. Does that mean my processor can support 64-bit?

That's my guess. There have been 64 bit Celeron chips around for years.

void.pointer · 2008-10-16 20:17:20

skottish wrote:

void.pointer wrote:
Wait a minute... If my processor couldn't support x86_64, wouldn't Archlinux fail to install/work? It's been working flawlessly so far. Does that mean my processor can support 64-bit?
That's my guess. There have been 64 bit Celeron chips around for years.

Whew, okay. So I don't need to reinstall

Okay so we've established that skulltag-server is a 32 bit program. How can I find out what libraries are not 32-bit out of its dependencies? I'm also not familiar with how to tell pacman to grab 32-bit libraries. I normally just accept whatever it gives me, which I'm not sure what it is giving me.

skottish · 2008-10-16 20:26:40

Back on track...

Some of the dependencies for this program are not existing lib32 libraries from community, nor has anyone put together the dependencies for AUR.

Things that don't exist yet: flac, fmod, nasm, p7zip, timidity++

Things that are in community: lib32-gtk2, lib32-libjpeg, lib32-sdl

Pulling in the stuff from community will also bring in a whole bunch of other libraries too.

You can find good examples of how lib32 packages are made from ABS. Or you can go with a chroot environment. Either way there's a lot of work to be done before this program will run.

Last edited by skottish (2008-10-16 20:27:59)

void.pointer · 2008-10-16 21:03:16

skottish wrote:

Back on track...
Some of the dependencies for this program are not existing lib32 libraries from community, nor has anyone put together the dependencies for AUR.
Things that don't exist yet: flac, fmod, nasm, p7zip, timidity++
Things that are in community: lib32-gtk2, lib32-libjpeg, lib32-sdl
Pulling in the stuff from community will also bring in a whole bunch of other libraries too.
You can find good examples of how lib32 packages are made from ABS. Or you can go with a chroot environment. Either way there's a lot of work to be done before this program will run.

I think you're assuming I know a lot more than I really do

I've literally only been using linux for the past 2-3 months. I've been a Windows user my entire life. So, basically, I'm not very familiar with Archlinux either as a result, since I spend the first month using Ubuntu

When I do "pacman -S some_library", what am I getting? 32-bit or 64-bit libraries? What do you expect me to be doing with ABS, building all of the dependencies myself?

skottish · 2008-10-16 21:14:37

void.pointer wrote:

skottish wrote:
Back on track...
Some of the dependencies for this program are not existing lib32 libraries from community, nor has anyone put together the dependencies for AUR.
Things that don't exist yet: flac, fmod, nasm, p7zip, timidity++
Things that are in community: lib32-gtk2, lib32-libjpeg, lib32-sdl
Pulling in the stuff from community will also bring in a whole bunch of other libraries too.
You can find good examples of how lib32 packages are made from ABS. Or you can go with a chroot environment. Either way there's a lot of work to be done before this program will run.
I think you're assuming I know a lot more than I really do
I've literally only been using linux for the past 2-3 months. I've been a Windows user my entire life. So, basically, I'm not very familiar with Archlinux either as a result, since I spend the first month using Ubuntu
When I do "pacman -S some_library", what am I getting? 32-bit or 64-bit libraries? What do you expect me to be doing with ABS, building all of the dependencies myself?

I'm just use to having you around! Actually, this is how I learned too. I still have a long way to go...

I'm curious about something before you go any farther. In the file /etc/pacman.d/mirrorlist, all of the entries there end in x86_64, right? For instance:

Server = http://archlinux.unixheads.org/$repo/os/x86_64

Last edited by skottish (2008-10-16 21:15:26)

void.pointer · 2008-10-16 21:17:14

skottish wrote:

I'm just use to having you around! Actually, this is how I learned too. I still have a long way to go...
I'm curious about something before you go any farther. In the file /etc/pacman.d/mirrorlist, all of the entries there end in x86_64, right? For instance:
Server = http://archlinux.unixheads.org/$repo/os/x86_64

Yes sir. The mirror at the top of my list is:

Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/x86_64

skottish · 2008-10-16 21:33:12

Oh good. I didn't want your system my first major mistake of the day!

There are three ways you can about this if you really want skulltag.

1) Rebuild your system as 32 bit
2) Install enough 32 bit libraries to run the thing. There are two options:
a) lib32 libraries (or the like)
b) chroot ( http://wiki.archlinux.org/index.php/Arc … bit_system )

I can tell you the lib32 method is going to be a lot of work, and will probably get you up to 100 or so 32 bit libraries. I've never set up a chroot before, but a lot of people seem to think that it's really straight forward.

Arch Linux

#1 2008-10-16 03:02:05

Skulltag server

#2 2008-10-16 03:11:10

Re: Skulltag server

#3 2008-10-16 12:41:24

Re: Skulltag server

#4 2008-10-16 14:16:50

Re: Skulltag server

#5 2008-10-16 14:44:31

Re: Skulltag server

#6 2008-10-16 15:26:58

Re: Skulltag server

#7 2008-10-16 15:30:04

Re: Skulltag server

#8 2008-10-16 16:19:24

Re: Skulltag server

#9 2008-10-16 16:22:30

Re: Skulltag server

#10 2008-10-16 16:33:24

Re: Skulltag server

#11 2008-10-16 16:36:06

Re: Skulltag server

#12 2008-10-16 16:40:02

Re: Skulltag server

#13 2008-10-16 16:41:47

Re: Skulltag server

#14 2008-10-16 20:05:05

Re: Skulltag server

#15 2008-10-16 20:07:03

Re: Skulltag server

#16 2008-10-16 20:17:20

Re: Skulltag server

#17 2008-10-16 20:26:40

Re: Skulltag server

#18 2008-10-16 21:03:16

Re: Skulltag server

#19 2008-10-16 21:14:37

Re: Skulltag server

#20 2008-10-16 21:17:14

Re: Skulltag server

#21 2008-10-16 21:33:12

Re: Skulltag server

Board footer