Compile error - make[2]: *** No rule to make target `libspeex/speex/ogg.h

[Flake_8]

I tried compiling rockbox from source over the last few days. I have had several compile errors after "make" depending on the daily build date. I tried reinstalling cygwin based on the "How To Compile" Wiki and am still getting the same errors.

For the latest daily build (2007-02-11) I get the following error after configure, and make for iaudio X5:

OBJCOPY aiff.codec
make[2]: *** No rule to make target `libspeex/speex/ogg.h', needed by `/home/User/rockbox/build/apps/codecs/speex.o'.  Stop.
rm /home/User/rockbox/build/apps/codecs/codec_crt0.o
make[1]: *** [build-codecs] Error 2
make: *** [all] Error 2


For the daily builds for 2-8, 2-9, and 2-10 I get the following error after configure and make:

CC bookmark.c
In file included from bookmark.c:38:
recorder/icons.h:28:25: rockboxlogo.h: No such file or directory
recorder/icons.h:30:32: remote_rockboxlogo.h: No such file or directory
make[1]: *** [/home/User/rockbox-20070210/build/apps/bookmark.o] Error 1
make: *** [all] Error 2

The daily build for 2-7 works fine. Are these types of compile errors common from day to day or is there something I am doing wrong?

[Llorean]

Try using SVN to check out the sources, rather than trying to build from the daily archive. It's not uncommon that when the source tree changes the script that makes the archive will fail to include everything.

If you actually use SVN as is suggested you'll never have this problem.

[safetydan]

Also, if you're using the same build directory, make sure you do a "make clean" before building again. This might clear the error for you.

[bluebrother]

Also, sometimes there are changes to the configure script that require you to re-run it. At least for the sim there was such a change recently (caused by the inclusion of speex). If in doubt try rerunning configure, at least it won't hurt.

[Flake_8]

Thanks for the tips. Using SVN fixed all the problems.
For some reason I had thought that the daily builds were more stable than the very latest svn build, but I can see I misunderstood how the versioning system works.

[Llorean]

Daily builds are entirely automated. There's no selection process that would make them more or less stable.

[bascule]

Thanks for the tips. Using SVN fixed all the problems.
For some reason I had thought that the daily builds were more stable than the very latest svn build, but I can see I misunderstood how the versioning system works.

This is a common mis-understanding that I also originally had.

I believe that the original intention was that no-one would commit a change likely to cause build or operating errors late in the day, such that they were not fully tested before the daily build was automatically compiled. This would ensure, albeit only procedurally, that daily builds were more likely to be stable.

f you look at the commit log, you will see that sometimes a change is backed-out or corrected after committing. If you happened to create a daily build before the bug was caught, you would potentially have an unstable build in your hands.

[Job Van Dam]

OBJCOPY aiff.codec
make[2]: *** No rule to make target `libspeex/speex/ogg.h', needed by `/home/gri
z/rockbox-devel/build/apps/codecs/speex.o'.  Stop.
rm /home/griz/rockbox-devel/build/apps/codecs/codec_crt0.o
make[1]: *** [build-codecs] Error 2
make: *** [all] Error 2

Gigabeat F20, I'm getting this error as well.
I just downloaded the Feb 13th source from the Daily builds page and the latest sourcethis page, updated to arm-elf-gcc 4.0.3 (you just gotta run Cygwin setup again and chose to install it right?), and did a 'make clean'.
Still I get the error above. Is there anything else I can try?

[bluebrother]

tried using svn? There were some files missing in the tarball.

[Job Van Dam]

I didn't use SVN I just used today's Current Build. What's the difference between SVN and the Current Build?

I though SVN and Current Build were the same just that SVN does the work for you.

[bluebrother]

the daily tarball is created using a list of files to package into it. Sometimes a file gets forgotten upon addition, and thus a daily tarball might miss some files. When using svn you'll always get the complete sources (and additional stuff svn itself saves, for example it gives you the possibility to diff against the svn checkout without keeping an additional copy of the files yourself)