>>> Unpacking source...
>>> Unpacking thunderbird-2.0b2-source.tar.bz2 to /var/tmp/portage/x11-plugins/enigmail-0.94.3-r1/work
>>> Unpacking mozilla-thunderbird-2.0_beta2-patches-0.2.tar.bz2 to /var/tmp/portage/x11-plugins/enigmail-0.94.3-r1/work
* Unpacking enigmail-de-0.9x.xpi to
/var/tmp/portage/x11-plugins/enigmail-0.94.3-r1/work
* Applying various patches (bugfixes/updates) ...
* Done with patching
>>> Unpacking enigmail-0.94.3.tar.gz to /var/tmp/portage/x11-plugins/enigmail-0.94.3-r1/work/mozilla/mailnews/extensions
* Applying 50_enigmail_no_upgrade-1.patch ...
[ ok ]
* Applying 70_enigmail-fix.patch ...
[ ok ]
* Running eautoreconf in
'/var/tmp/portage/x11-plugins/enigmail-0.94.3-r1/work/mozilla' ...
* Running autoconf ...
[ ok ]
>>> Source unpacked.
...
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:
nsCOMPtr.o: relocation R_X86_64_PC32 against
`nsGetServiceByContractIDWithError::operator()(nsID c
onst&, void**) const' can not be used when making a shared object; recompile
with -fPIC
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld:
final link failed: Bad value
collect2: ld returned 1 exit status
gmake[2]: *** [libxpcom_core.so] Error 1
Found out that that's due to bumping to
mozilla-thunderbird-2.0_beta2-patches-0.2.tar.bz2. The patches are virtually
the same as in the 0.1-patchset, however in 0.1 they were bzipped and in 0.2
they are not.
Looking at the corresponding changes in the
mozilla-thunderbird-2.0_beta2.ebuild the line EPATCH_SUFFIX="patch" has to be
added to the enigmail ebuild then the mozilla-thunderbird patches are applied
properly and enigmail compiles.
And why don't bump the patchset to 0.4 ? Compiled here as well
gcc-4.1.2 x86_64-pc-linux-gnu
Reproducible: Always
