This is precisely what osx-build.sh (in packaging/macosx/) is there
for. Would you care to comment on why you don't use it?

Hello men,

sorry for answering so late.

And another sorry for not facing the challenge of another compiling orgy, as I see it's quite complicated, and I found a workaround for my problem. I'll keep to the aqua thing…

But maybe all your work and effort is not lost, probabely ~suv and I ran into the same trap:

As Mac people like to have things very easy, we can easily get lost if there is a clear instruction. So, if a Maccie reads the README (yes, some Maccies do so…), he finds:

Inkscape uses the standard procedure for compilation and installation: 

  ./configure
  make
  make install

If a "./configure" file is not present, you can create it by running
the "./autogen.sh" command, which calls in turn a number of other
programs such as automake and autoconf.  See INSTALL for more
details. 

At this point I forgot that on a Mac there is much more about it - allthough I fought myself all the way to an inkscape aquaalpha… - 
So it might be helpful to add a sentence like "Mac OS X users please have a close look at the wiki pages under http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX. You should use macports to make it work… etc"

Thanks for your support - looking forward to 0.47 anyways!

Greetings,

Wolf