Rockbox Development > Starting Development and Compiling

SVN Errors Within Cygwin

(1/4) > >>

Kalbintion:
Getting the following list of error feed when attempting to make the latest build via Cygwin. All works according to the Simple Guide to Compiling up until the 'make' portion (Specifically, section 3 B is when it speaks of using the 'make' command). Not exactly sure why, seeing as i cd into the recommended folder name, build under the rockbox development directory (in my case its G:/rockbox/, and build directory being G:/rockbox/build/) and creating the build without any errors at all...


--- Code: ---svn: '\cygdrive\g\rockbox' does not exist
svn: '\cygdrive\g\rockbox\tools' does not exist
Generating dependencies
/bin/sh: /cygdrive/g/rockbox/tools/addtargetdir.pl: /usr/bin/perl^M: bad interpreter: Invalid argument
Can't open perl script "/cygdrive/g/rockbox/tools/multigcc.pl": No such file or directory
Can't open perl script "/cygdrive/g/rockbox/tools/multigcc.pl": No such file or directory
/bin/sh: /cygdrive/g/rockbox/tools/addtargetdir.pl: /usr/bin/perl^M: bad interpreter: Invalid argument
Can't open perl script "/cygdrive/g/rockbox/tools/multigcc.pl": No such file or directory
/bin/sh: /cygdrive/g/rockbox/tools/addtargetdir.pl: /usr/bin/perl^M: bad interpreter: Invalid argument
svn: '\cygdrive\g\rockbox' does not exist
svn: '\cygdrive\g\rockbox\tools' does not exist
CC tools/rdf2binary
make: gcc: Command not found
make: *** [/cygdrive/g/rockbox/tools/rdf2binary] Error 127

--- End code ---

torne:
Your line endings are being interpreted incorrectly. Did you select unix or dos line endings when you installed cygwin, and what are you using to get the source?

Kalbintion:
Whatever the default line endings would be is what I would guess Cygwin selected. As i do not recall ever actually selecting any specific one when installing it. And i am using SlikSVN x86 (32 bit) (http://www.sliksvn.com/en/download/) to acquire the source code via the CMD Shell in Win XP SP3, which honestly, are they (the SVN programs) not all the same in essence in acquiring the files?

torne:
Windows SVN programs will download the files with DOS line endings. The command line svn program in Cygwin will download the files with UNIX line endings. You will probably find it works if you check out the code with Cygwin's command line svn. You may also be able to get it to work by changing Cygwin's line ending settings but this is a bit of a nasty hack. Cygwin defaults (correctly) to UNIX line endings as this is the only option guaranteed to behave consistently.

Kalbintion:
Which I'd assume goes back to the whole fact that Windows uses 2 bytes to indicate a line return where Unix uses one... If so, life is life and that problem is easily fixable for me. I have no problem using a compatible text editor on Windows, I do enjoy programming on Win, *Nix, and Mac systems simultaneously :)

But, to which what you had said. Using the built-in svn command of cygwin is still causing the make to fail with the same lines as my original post.

Navigation

[0] Message Index

[#] Next page