app-arch/bzip2 currently has a rather convoluted and unportable
ebuild due to upstream using a pair of handwritten Makefiles in
stead of a more standard autotools setup.
Stanislav Brabec <firstname.lastname@example.org> has already laid most of the
groundwork in setting up an autotool package for it, and with
the guidance of Soap a git repo was created with gentoo's own
bzip2 patches and the autotools setup incorporated in a sane way.
Both of my attempts to contact the original author J. Seward at
both email@example.com and firstname.lastname@example.org resulted in the mail
bouncing back as undeliverable.
As it currently stands, without these changes to a more portable
autotools setup, using chrossdev to compile for mingw-w64 will
result in a libbz2.so which is actually a PE32 dll and bzip2
which is also a PE32 executable without a .exe extension.
In addition, changing the build system will result in a much
simpler and easy to maintain ebuild, and adds pkg-config support,
a feature which has been missing from bzip2 its entire life.
Please also try contacting the upstream author at email@example.com .
(In reply to Felix Janda from comment #1)
> Please also try contacting the upstream author at firstname.lastname@example.org .
Oh, nice. I had tried emailing both email@example.com and firstname.lastname@example.org,
but both emails got bounced back as deliverable. I will give that email
a shot as well.
@ Mike Frysinger: Please comment on that fact that new bzip2 package would lose USE=static. Is this a problem?