As long as you're not able to compile, I'm not sure we want to use your ebuild :)

Besides, I was under the impression that the ebuild in the wiki had been updated recently?

Since it is basically *your* ebuild, with just errors fixed and style corrected, I doubt it introduced any bugs…

Though if you could provide me with working compilation instructions (or fix your ebuild), the ebuild would even compile…

Compilation instructions are available at http://www.rockbox.org/twiki/bin/view/Main/RockboxUtilityDevelopment

I don't know of any core Rockbox devs who use Gentoo, but there was some discussion in the IRC channel recently which might be useful to read (2008-08-19 and 2008-08-21). At any rate, this is going to rely on a user getting it right.

That ebuild is not "our" ebuild but contributed – it's in the wiki, and anyone can attach files to the wiki. It looks like you're using additional CCOPTS / CXXOPTS that cause problems – building works fine for me from a clean svn checkout.

CFLAGS= CXXFLAGS= emerge -1 rbutil « Fails as well, so it seems not to be related to any CFLAGS/CXXFLAGS. Additionaly the flags I use are rather conservative, and if they imposed a problem to your code, there would be something rather wrong.
And that still would not explain why the generation of translations is broken or why something tries to pass "amd64" to gcc (I do not do that).

emerge –info:

Portage 2.2_rc8 (default/linux/amd64/2008.0/desktop, gcc-4.3.1, glibc-2.8_p20080602-r0, 2.6.26-gentoo-r1 x86_64)

Would you please attempt to build according to the build instructions in http://www.rockbox.org/twiki/bin/view/Main/RockboxUtilityDevelopment?

Try building Qt manually if this still fails.

just to make this clear: the generation of languages is NOT broken. What you're seeing is a warning that gets triggered as the translation files aren't present when the build starts. They get generated slightly later (by the lrelease call), and the resource file containing them gets generated even later. Thus there is only a slightly annoying warning, but this doesn't affect the build process in any way. The wiki page has this behaviour noted, so please check the documentation first.

oh, and another thought: are you *absolutely* sure the qmake you're calling is actually qt4's qmake? Running Qt3's qmake won't produce an error but create broken Makefiles, thus the succeeding build will fail.

I think I found the issue.

The variable ARCH, which you use in tools/rbspeex/Makefile, is also used by Gentoo and there set to "amd64". (Try running "make ARCH=amd64".)
This will generate the behaviour I experienced.

Running 's/ARCH/RBARCH/' over that file will make the issue not appear anymore.

The attached ebuild hacks around the issue (via sed in src_unpack()), and also has some further, unrelated, style improvements.

   rbutil-9999-r1.ebuild (1 KiB)

Maybe we should fix this in the real Makefile, instead of hacking around it in the ebuild..

Thought so. ;)

I just commited the fix with the renaming of the ARCH define into SVN.