[FIXED]Can't Compile on 5G SVN due to alarm_menu.c?

[Thecoolgman]

I've started using SVN for compiling since the current build is gone And I have this issue when compiling: And no I do not have an patches that affect the alarm menu.

[saratoga]

Do you have any patches at all? 

[Thecoolgman]

I have done a clean build and got the same thing. I don't know what's going on.

[Blue Dude]

It looks like it might be a problem with english.lang, and it just happens to show up in the alarm menu.

Start completely from scratch:
svn up
cd build
make reconf
make clean
make

A change in a language file can sometimes compile funky, but make clean should take care of it.  If you've applied any patch that affects a language file, it might fail again.  If all this fails, check out a completely new working copy to another directory and build from that.

[Thecoolgman]

No that did not work. Ugh, my head hurts.

[linuxstb]

How did you checkout the source from SVN?  Did you use the command-line "svn" from within cygwin, or a GUI SVN program, such as tortoisesvn?

apps/alarm_menu.c is suspiciously early in the alphabet, which makes me think it's the first file using language strings that fails.  One problem could be that you've checked out the source code using Windows-style line endings (i.e. CR and LF), whereas your cygwin install is configured to use Unix-style line endings (i.e. just LF).  This can cause strange things to happen.

[Thecoolgman]

I used Tortoise SVN and used this tutorial in the wiki: http://www.rockbox.org/twiki/bin/view/Main/UsingCygwinAndTortoiseSVN

[linuxstb]

I used Tortoise SVN and used this tutorial in the wiki: http://www.rockbox.org/twiki/bin/view/Main/UsingCygwinAndTortoiseSVN

So your cygwin is definitely configured to use DOS (CR+LF) line endings?

I'm not sure how you can check, but maybe just typing "echo > a.txt" will tell you.  If the resulting a.txt file is 1 byte in size, then you're still using Unix line-endings, if it's two bytes, then it's correctly configured with CR+LF.

[gevaerts]

Please verify that your build directory is entirely empty before you run configure

[Thecoolgman]

So your cygwin is definitely configured to use DOS (CR+LF) line endings?

I'm not sure how you can check, but maybe just typing "echo > a.txt" will tell you.  If the resulting a.txt file is 1 byte in size, then you're still using Unix line-endings, if it's two bytes, then it's correctly configured with CR+LF.

I think I found the problem. It came out 1 KB like you said. Should I just Delete my Cygwin Folder and instal again using CR+LF?