There is currently no way using portage to create a static mod_perl linked with the apache binary. Certain packages like HTML-Mason *require* mod_perl to be static instead of a DSO. Is there a way the mod_perl ebuild can be modified to build a static mod_perl if the "static" USE flag is in effect? I've written a few simple ebuilds before, but I don't have enough experience to do this myself.
Steps to Reproduce:
I'll assume you're referring to MP 1.x series as MP 2 is meant to be a DSO.
Currently, this doesn't seem possible as the only real way to do this is to add a local mod_perl use flag to apache that, if set, drags in the mod_perl source and builds it under the guise of apache. This could be done and dev-perl/mod_perl could be fulfilled as a virtual. In that instance, it might work, but it would add a certain level of complexity to the situation and potentially cause problems with numerous other ebuilds. On top of this, it could only be done with apache-1.* series ebuilds.
Outside our scope for the time being.