Strange error with the server host.

[Profile]

I keep getting this error when giving permission to "configure". Due to this, I can't proceed the migration to a paid host.

[root@intelig1-4 emulador]# ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define _EXTENSIONS_... yes
checking whether make sets $(MAKE)... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking for ar... /usr/bin/ar
checking whether byte ordering is bigendian... yes
configure: error: bigendian is not supported... stopping

The host doesn't know how to fix this, apparently they have installed an rAthena server in the past month and had no issues.

I tried switching to a clean version of rAthena and the error still persists.

 

Could anybody give me some assistance? Thank you!

 

Edited June 28, 2017 by Profile

[Functor]

https://github.com/rathena/rathena/issues/2127

[Profile]

Thank you Functor, will ask the provider to check that out.

[Profile]

The problem has been solved!

[danizinx]

Up, i have the same problem in my linux.. and not solved, I tried everything already https://github.com/rathena/rathena/issues/2127