You're receiving this canned (template-based) bug report because I found a problem with a package during my tinderbox run.
The package in question is running automake (and most likely other autotools) during compile phase by maintainer-mode. You can see in my blog post in the URL field why that's a problem, and how to address the issue, but in general, you don't want maintainer-mode rebuild during compile phase, especially since it can cause multiple run of econf.
The causes of maintainer-mode rebuild are various, but most likely it's because of a patch that changes Makefile.am or configure.ac/in and don't rebuild autotools properly. The way to fix this is almost always to inherit autotools eclass and run eautomake/eautoreconf (as needed; eautoconf should only be used when automake is not involved, which is not the case here) during src_unpack phase.
Created attachment 179251 [details]
this ebuilds uses kde.eclass to do actual work. So it's not potrace but
kde.eclass needs to be fixed.
(In reply to comment #2)
> this ebuilds uses kde.eclass to do actual work. So it's not potrace but
> kde.eclass needs to be fixed.
One can entertain the idea to run checks, if a patch is applied, but there are other ways such changes can be done, e.g. by using a sed expression in the ebuild. This is something the developer modifying the ebuild is responsible to care for, I'm afraid.
Fixed. Up to maintainer team to call for stabilization of 1.3.4-r1 soon.