Noob question: ../tools/configure error in recent builds

[johnnyhaggis]

Hi - several months ago (may 2007 to be precise) working with the cygwin environment, I made several successful modifications to the then current rockbox build.   Recently I tried some of the same modifications on recent builds and I keep getting the same error when I do ../tools/configure from my build folder.

I double checked against my may 2007 version and there were no errors with that one.

The error list is:

../tools/configure: line 10: $'\r': command not found
../tools/configure: line 13: $'\r': command not found
../tools/configure: line 15: $'\r': command not found
../tools/configure: line 17: $'\r': command not found
../tools/configure: line 21: syntax error near unexpected token '$'{\r' '
../tools/configure: line 21: $'\r': 'input() {

I don't know what this means and thus am not in a position to know what to do about it.  The tools folder still has a configure file in it, so that can't be the problem.

Has there been a major change in the way rockbox is built so that the "Simple Guide to Compiling Rockbox" is no longer applicable?

Also, on my old build, when I changed the boot logo, using a 320x240 bitmap,there was a cyan horizontal bar maybe 15 pixels wide going across the top of the screen (I'm working with an ipod video 5.5) - anyone know why that happens?

I did several searches in this section of the forum but couldn't dind anything, though maybe this has already been addressed.  If so, apologies, and please point me to the correct thread.  

Thanks,

DB

[cool_walking_]

I think you've dos-ified your line endings. Use dos2unix.

[johnnyhaggis]

Hey thanks - unfortunately I'm too ignorant to know what you mean!  What do you mean by line endings?

And why would the command totally work with no problem on a source from may 2007, but not one from today?

[cool_walking_]

Dos/Windows, Mac, and Unix all use different characters to indicate the end of a line in a text file.  The dos2unix program (it should be in your cygwin environment already) will convert the line endings in all the files you give it to unix format.

Your files could have been converted to DOS format via a stupid .zip file program, you altering the files in a text editor, or a basically any process that touches the files.

[johnnyhaggis]

So you mean the fact that I used WinZip to unzip the source file would have messed up all the filenames?  So if I just decompress the source tar.br2 file with cygwin instead of WinZip it should work again?

I had no idea WinZip would be so meddlesome!

[cool_walking_]

WinZip could be responsible. I have no idea, I haven't used it in years. If you decompress the archive from within Cygwin, it should be fine, or you could just convert your existing source with dos2unix.

.. if that is actually the problem. I could be wrong.

[johnnyhaggis]

Indeed that was the problem, and WinZip was the culprit.  I unzipped it with WinRAR instead to see if there would be a difference, and this time it works.  I'll try using dos2unix on the messed up version and see if that works now.  Thanks so much!

[johnnyhaggis]

By the way - do you have any idea why there's a horizontal cyan bar on my altered boot logo?

[cool_walking_]

Sorry, no.

Also, if no-one has replied after you, you're supposed to edit your message instead of posting again.

[johnnyhaggis]

Oops - will do next time.  Thanks very much for solving my problem by the way, my build is happily compiling as I type, DB

[cool_walking_]

No problem  

EDIT: hrm. I've probably just ruined your chances of getting your other problem solved here by writing that conclusory statement. You might want to head to IRC for these questions, you'll get faster answers.