Red Hat Bugzilla – Bug 22427
problems building CPAN modules with standard perl
Last modified: 2007-04-18 12:30:14 EDT
Please see the description I posted to the guiness-list with the answer
from Jakub Jelinek who asked me to send a bugzilla.
Below is a list that locate sem.h prints on my machine:
$ locate sem.h
On Mon, Dec 11, 2000 at 01:34:12AM -0500, Kerem Yaman wrote:
> Does anybody know why I could be getting the following error when trying
> to install some CPAN packages on 7.0 standard perl installation. I have
> not played with Perl for a while (proabably since 5.2 or so). So I am
> not sure if this is a known problem or not. And I don't see a newer
> version of perl than I have on the errate pages.
> During make of MIME::Base64 I get:
> gcc -c -fno-strict-aliasing -O2 -march=i386 -mcpu=i686
> -DVERSION=\"2.11\" -DXS_VERSION=\"2.11\" -fPIC
> -I/usr/lib/perl5/5.6.0/i386-linux/CORE Base64.c
> In file included from Base64.xs:33:
> /usr/lib/perl5/5.6.0/i386-linux/CORE/perl.h:3205: redefinition of `union
> make: *** [Base64.o] Error 1
> /usr/bin/make -- NOT OK
> Running make test
> Can't test without successful make
> Running make install
> make had returned bad status, install seems impossible
> I also get it when installing other packages but this one does depend on
> other CPAN packages so I know the problem is in the redefinition of
> `union semun' line right here.
Please file this into http://bugzilla.redhat.com/bugzilla/
It might as well be bug in that Base64 code, glibc does not define union
semun in its headers, so Perl is correct in declaring it.
Maybe some source includes some kernel headers which define it (such as
<linux/sem.h>), that would be the bug.
I was not able to get these compile errors to occur on a standard 7.0 install
using perl-5.6.0-9. I was also unable to get this to happen on a machine running
fisher beta which now has perl-5.6.0-11 installed. Does this still occur if you
upgrade to the latest perl rpm from rawhide? Please try upgrading and reopen
this bug report if it still occurs.
Thanks, it was library conflicts on my machine causing the problem it works now.