There seems to be a bug somewhere in the Makefile: "Makefile:204: *** missing separator. Stop." Full build log attached
Created attachment 236799 [details] Build log
That log doesn't say much, attach that Makefile.
attach the emerge --info output as well
Created attachment 237131 [details] emerge --info
Created attachment 237133 [details] Makefile
Well, for the moment it seems that autoconf disagrees with the way AC_COPYRIGHT is used.
For me it failed to compile because it could not find Foomatic/Default.pm. Turns out in was at /usr/lib/perl5/vendor_perl/5.10.1/Foomatic rather than /usr/lib/perl5/vendor_perl/5.12.1/Foomatic. So I emerged net-print/foomatic-db-engine and then successfully emerged net-print/gutenprint.
(In reply to comment #7) > For me it failed to compile because it could not find Foomatic/Default.pm. > Turns out in was at /usr/lib/perl5/vendor_perl/5.10.1/Foomatic rather than > /usr/lib/perl5/vendor_perl/5.12.1/Foomatic. So I emerged > net-print/foomatic-db-engine and then successfully emerged > net-print/gutenprint. > Thank you. That worked great. For people curious as to how to find these missing .pm files for themselves, the emerge log will tell you when one is missing. Such messages usually take the form of: Can't locate Foomatic/Defaults.pm in @INC (@INC contains: {blah blah blah} Be sure you have gentoolkit installed and then do: equery b Missing_File.pm {i.e. equery b Defaults.pm} Look for the line containing the correct path fragment {i.e. Foomatic/Defaults.pm} and emerge the indicated package like so: # equery b Defaults.pm * Searching for Defaults.pm ... net-print/foomatic-db-engine-4.0.4 (/usr/lib64/perl5/vendor_perl/5.10.1/Foomatic/Defaults.pm) The generic issue appears to be related to how Perl pm files are generated and installed and doesn't really have anything to do with Gentoo. Following the above will allow you to fix the general problem correctly for yourself as you encounter specific instances.
this is probably no longer an issue with 5.2.6 which is already on the tree and tagged also for ~ARCH, so maybe no longer relevant? beware that 5.2.6 also fails to build (at least on ~amd64, but likely all other arch too) for different reasons though as shown in BUG362943
This should be fixed in versions currently in the tree.
