Crystal Space Compiling from source in Ubuntu error

[quazi_farhan]

Hello,

I downloaded source code of Crystal Space, cal3d, planeshift from svn and tried to compile as this guide says : http://planeshift.svn.sourceforge.net/viewvc/planeshift/trunk/docs/compiling.html . After successfully compiling cal3d when I try to compile crystal space, the following error occurs.

Code: [Select]

root@Nexus:~/planeshift/cs# ./configure --enable-debug --without-java --without-perl --without-python --without-3ds --with-cal3d=$HOME/planeshift/cald3
configure: error: cannot run /bin/bash mk/autoconf/config.sub
I have setup all the packages required as mentioned by this command.

# sudo apt-get --assume-yes install libjpeg62-dev x11proto-gl-dev autoconf jam bison libcurl3-dev flex-old automake1.9 libcurl4-openssl-dev libmng-dev libmikmod2-dev libogg-dev libvorbis-dev zlib1g-dev libpng12-dev build-essential libtool libglu1-mesa-dev libglu1-xorg-dev xserver-xorg-dev libxt-dev libopenal0a libopenal-dev subversion zlibc libttf2 libfreetype6-dev libfreetype6 libasound2-dev alsa-oss libxxf86vm-dev libxext-dev x11proto-xext-dev libspeex-dev

Can anyone tell me any solution?

[weltall]

either permission issue or the files aren't there

[quazi_farhan]

bin/bash is certainly there. And I am running it as a root. So permission should not be a problem. Anyway, the issue seems to be with a parameter as " mk/autoconf/config.sub " . My actual concern is what this might be?

[quazi_farhan]

Okay, as for mk/autoconf/config.sub , mk is a directory in Crystal Space folder itself. but the autoconf sub-directory and config.sub are already there. so why bin/bash wont be able to access it ?

[quazi_farhan]

Okay, it has been resolved. The svn checkout was performed in windows, hence all the file's carriage return was in windows format and bash could not handle it. Manually downloading the text files from svn has solved it. Some has suggested  the tool "tofrodos" can be used to convert between UNIX and windows format.

[weltall]

better to always download files from the os you are going to use to build as we use native carriage return.
also being root doesn't mean you can run things (flags sets off or disabled from mount will forbid also root from doing things, till he changes those flags at least)