Bagder and I just helped someone on the IRC channel track this down.
(sorry, no idea what Bagder's real name is, darned IRC)
It turns out apple have made a funtastic change to the default operation
of their GNU c preprocessor, which rockbox uses to generate a list of
files to include for compilation.
They forced the preprocessor to add a #pragma line to the beginning of
output, for some reason to do with xcode (why this should be a default
then is puzzling, but nevetheless)
It can be worked around by modifying the makefiles that reference
something similar to
SRC := $(shell cat SOURCES | gcc -DMEMORYSIZE=$(MEMORYSIZE) $(INCLUDES)
$(TARGET) $(DEFINES) $(EXTRA_DEFINES) -E -P -include "config.h" - )
SRC := $(shell cat SOURCES | m68k-elf-gcc -DMEMORYSIZE=$(MEMORYSIZE)
$(INCLUDES) $(TARGET) $(DEFINES) $(EXTRA_DEFINES) -E -P -include
"config.h" - )
(or whatever for archos/gmini, which will have sane preprocessor
operation. this needs to go into several makefiles however.)
there's all sorts of mentions of it and issues it's caused if you search
#pragma GCC set_debug_pwd
there might well be a cleaner solution to this tho, but this works as a
On Tue, 2005-02-22 at 10:57 +0100, Svante Tidholm wrote:
> Hi Ben,
> Im also a Mac OS X 10.3.8 user, and get the same error as you. I
> think this is a Mac connected problem since no one else get the same
> error. I don't have any solution for this problem, just wanted you to
> know that you're not alone. Hope someone figures it out. I've tried
> all possible solutions solving it by starting fresh, so my only
> conclusion is that it means that all of a sudden rockbox started
> relying on something that Mac OS X doesn't offer...
> >Hi all,
> >I'm running into a problem compiling the latest Rockbox CVS. When I do a
> >make for a Recorder 20 model, I getting the following error:
> > make: *** No rule to make target `#pragma', needed by
> >`/Users/ben/Projects/rockbox/rockbox/build-dir/dep-firmware'. Stop.
> > make: *** [all] Error 2
> >I'm running Mac OS 10.3.8. I am able to compile 2.3 and 2.4 releases
> >without a problem. I've deleted the entire directory and checked out the
> >latest code and gotten the same problem. Any suggestions?
Received on Tue Feb 22 14:35:54 2005