I can go ahead and grab/compile automake 1.8.x and give it a go. I have a feeling that the build system is a bit messed up as I'm using some items from Debian packages and some self-compiled. Invariably this causes problems, but attempting to purge my system of the Debian versions makes APT want to uninstall my entire system (everything depends on gcc!).
Looks like it's time to roll my own distro.
I'll post the results when I run an automake 1.8 compile.
The hackers on this list obviously know what they're doing :)
I went ahead and grabbed automake 1.8.5, wiped my sandbox to get rid of the files that I moved around, and compiled Inkscape from CVS without a hitch. Thanks to everyone that helped out with this! Inkscape has a fantastic community!
So, just for the record, automake 1.9.x worked for me overall except that any mmx optimizations would cause make to error due to the misplacing of .o files. I was able to got around the problem in three ways:
1) Compile Inkscape without mmx optimization (not my favorite solution) 2) Manually move all *_mmx*.o files from @TOPSRCDIR@/src/ to @TOPSRCDIR@/src/libnr/ when make fails (not difficult or particularly time consuming, but annoying nonetheless) 3) Regress to 1.8 series of automake (the simplest and most reliable in the end, but it's always a shame when tools aren't backwards compatible)
I wish I knew why automake is the buggy link in the chain, or why in only has issues with mmx support. Don't hold me to this, as I'm not all that familiar with the tool (and I only have limited programming experience), but I'll try compiling with automake 1.9 again and examining the results. If I come up with anything of merit, I'll post it.
Again, thanks for all the help, guys. I love Inkscape and I'm looking forward to doing more bug hunting and whatever else I may for the project.
-- Seth Brutzman deadlyhead@...952...