Compiling on ARM| Unrecognized Command

General help and assistance forum.
Post Reply
ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

Compiling on ARM| Unrecognized Command

#1

Post by ODROID » Wed Oct 30, 2013 6:18 pm

Hey everyone, my first post since the beggining of skulltag and also zandronum, since I've been looking around as a guest ever since, until today.
My problem is not because of FMOD, OGL, X11, I have all those installed and in working condition, I have all the preresquites but at 19% it gives me an unrecognized error, see the following link http://pastebin.com/9RYyY3GK for more detailed information. Reason why it's shorter is because I failed and closed the terminal and tried again with no success.

User avatar
Torr Samaho
Lead Developer
Posts: 1543
Joined: Fri May 25, 2012 6:03 pm
Location: Germany

RE: Compiling on ARM| Unrecognized Command

#2

Post by Torr Samaho » Wed Oct 30, 2013 7:12 pm

Looks like SSE is not supported on your platform, so you need to adjust dumb/CMakeLists.txt and possibly dumb/src/it/filter.cpp. I'm pretty sure that Zandronum's ZDoom base is not ARM compatible (and I don't know if even the latest ZDoom version is ARM compatible), so expect to change numerous things if you want to compile it on ARM.

ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

RE: Compiling on ARM| Unrecognized Command

#3

Post by ODROID » Wed Oct 30, 2013 7:29 pm

I thank you for your detailed response, I will take a look at it and do my best!

ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

RE: Compiling on ARM| Unrecognized Command

#4

Post by ODROID » Wed Oct 30, 2013 10:40 pm

I've gotten by the architechture problems but now the FPU Extended and Double is giving me problems, as such in this pastebin, http://mibpaste.com/w0yUmJ
I can also see you noted in D_Main.cpp that the math variance might get cropped, gcc.

// Set the FPU precision to 53 significant bits. This is the default
// for Visual C++, but not for GCC, so some slight math variances
// might crop up if we leave it alone.
#if defined(_FPU_GETCW)
{
int cw;
_FPU_GETCW(cw);
cw = (cw & ~_FPU_EXTENDED) | _FPU_DOUBLE;
_FPU_SETCW(cw);
}
#elif defined(_PC_53)
// On the x64 architecture, changing the floating point precision is not supported.
#ifndef _WIN64
int cfp = _control87(_PC_53, _MCW_PC);
#endif
#endif

Blzut3
Developer
Posts: 308
Joined: Thu May 24, 2012 9:37 pm

RE: Compiling on ARM| Unrecognized Command

#5

Post by Blzut3 » Thu Oct 31, 2013 12:17 am

Torr Samaho wrote: and I don't know if even the latest ZDoom version is ARM compatible
ARM is bi-endian IIRC so it should work taking care to remove the x86isms (turning on SSE, disabling the ASM). Zandronum 2.0 should definitely work fine since PowerPC support was added to ZDoom at that point so in theory the endian issues are taken care of there.

User avatar
Torr Samaho
Lead Developer
Posts: 1543
Joined: Fri May 25, 2012 6:03 pm
Location: Germany

RE: Compiling on ARM| Unrecognized Command

#6

Post by Torr Samaho » Thu Oct 31, 2013 7:29 am

Blzut3 wrote: ARM is bi-endian IIRC so it should work taking care to remove the x86isms (turning on SSE, disabling the ASM). Zandronum 2.0 should definitely work fine since PowerPC support was added to ZDoom at that point so in theory the endian issues are taken care of there.
Thanks for the info!

ODROID, are you trying to compile the latest 2.0 alpha or 1.2?

ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

RE: Compiling on ARM| Unrecognized Command

#7

Post by ODROID » Thu Oct 31, 2013 1:40 pm

I was trying to compile 1.2, I assume now 2,0 would be my best bet.
How to disable ASM and remove all x86 strings? I was putting -mlittle-endian as arch and that's how far I got with 1.2.
--Edit--
Where is 2.0 source :P?
Last edited by ODROID on Thu Oct 31, 2013 1:43 pm, edited 1 time in total.

Blzut3
Developer
Posts: 308
Joined: Thu May 24, 2012 9:37 pm

RE: Compiling on ARM| Unrecognized Command

#8

Post by Blzut3 » Thu Oct 31, 2013 5:21 pm

ODROID wrote: How to disable ASM and remove all x86 strings? I was putting -mlittle-endian as arch and that's how far I got with 1.2.
There's a NO_ASM switch in CMake which disables the ASM. For SSE you'll need to look in src/CMakeLists.txt and find where we're enabling SSE optimizations and turn them off.
ODROID wrote: Where is 2.0 source :P?
Just grab the latest version from the main Mercurial repository.

User avatar
skyrimguy
 
Posts: 86
Joined: Sun Jul 29, 2012 8:35 am

RE: Compiling on ARM| Unrecognized Command

#9

Post by skyrimguy » Thu Oct 31, 2013 9:01 pm

Blzut3 wrote: There's a NO_ASM switch in CMake which disables the ASM.
Which one?

-DNO_ASM=1
-DNO_ASM=ON
-DNOASM
Last edited by skyrimguy on Thu Oct 31, 2013 9:02 pm, edited 1 time in total.

Blzut3
Developer
Posts: 308
Joined: Thu May 24, 2012 9:37 pm

RE: Compiling on ARM| Unrecognized Command

#10

Post by Blzut3 » Fri Nov 01, 2013 1:03 pm

Either of the first two should work, but -DNO_ASM=ON is typically what's used.

If you're ever not sure about a cmake setting there's always cmake -i, ccmake, or cmake-gui. ;)

ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

RE: Compiling on ARM| Unrecognized Command

#11

Post by ODROID » Fri Nov 01, 2013 9:49 pm

Thanks everyone, Thank you all for your kindness and patience.
But for today, I've been experiencing high wind speeds making the power go out on and off all day. I will continue on this tomorrow. I'm about to check cmake-gui. Never thought cmake had a ui.

ODROID
New User
Posts: 8
Joined: Wed Oct 30, 2013 6:12 pm

RE: Compiling on ARM| Unrecognized Command

#12

Post by ODROID » Wed Nov 06, 2013 12:35 pm

Now all I'm waiting for is a bigger and faster SD card, as I'm using as of now a 4GB SD Card Class (4), which is painfully slow for SoC computers. My 8GB recently died or as other people say "Ran out of cycles and turned read only?" Once I get it, I'll compile this with some results asap.

Post Reply