Date: Sun, 18 Jul 2004 18:06:23 -0700 (PDT) From: David Newman <dnewman@networktest.com> To: Anders Nordby <anders@FreeBSD.org> Cc: tobez@FreeBSD.org Subject: Re: Perl 5.8.4 issues in FreeBSD 4.10-RELEASE Message-ID: <20040718180520.C97857@saronni.int.networktest.com> In-Reply-To: <20040718194326.GA81260@totem.fix.no> References: <20040718194326.GA81260@totem.fix.no>
next in thread | previous in thread | raw e-mail | index | archive | help
I built a 4.10 box the other day and installed perl 5.8.4 from ports -- no errors. Did you cvsup your ports collection before doing the install? dn On Sun, 18 Jul 2004, Anders Nordby wrote: > Hi tobez@, perl@, > > I found a couple of problems/oddities with the FreeBSD port for Perl > 5.8.4 using FreeBSD 4.10-RELEASE. I want to know if you are aware of > them and/or are working on a fix. I'll file a PR with more information > if you want. > > It's not building: > > ---snip--- > Making MIME::Base64 (dynamic) > Writing Makefile for MIME::Base64 > cp QuotedPrint.pm ../../../lib/MIME/QuotedPrint.pm > cp Base64.pm ../../../lib/MIME/Base64.pm > ../../../miniperl "-I../../../lib" "-I../../../lib" > ../../../lib/ExtUtils/xsubpp -typemap ../../../lib/ExtUtils/typemap > Base64.xs > Base64.xsc && mv Base64.xsc Base64.c > cc -c -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.4/BSDPAN" > -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing > -I/usr/local/include -O -pipe -DVERSION=\"3.01\" > -DXS_VERSION=\"3.01\" -DPIC -fPIC "-I../../.." Base64.c > Base64.xs: In function `XS_MIME__Base64_decode_base64': > Base64.xs:224: `dowarn' undeclared (first use in this function) > Base64.xs:224: (Each undeclared identifier is reported only once > Base64.xs:224: for each function it appears in.) > *** Error code 1 > > Stop in /usr/ports/lang/perl5.8/work/perl-5.8.4/ext/MIME/Base64. > *** Error code 1 > ---snip--- > > I solved this temporarily by removing the check of whether dowarn is set > in work/perl-5.8.4/ext/MIME/Base64/Base64.xs. This does not seem to > happen when I install in an empty, clean 4.10-RELEASE sandbox however. > :-X Not sure why. But I do see by Googling that others have/had the same > problem. Anyway, yes, I did completely uninstall any perl ports before > building ports/lang/perl5.8 here. And the OS/jail where I cannot build > perl5.8 does have fresh include/share/libdata dirs without old, stale > files. > > 2) After installing it and running use.perl port, perl does not run > anymore if you set LD_LIBRARY_PATH: > > # perl -v > /usr/libexec/ld-elf.so.1: perl: Undefined symbol "PL_exit_flags" > > By moving /usr/lib/libperl* out of the away, or unsetting > LD_LIBRARY_PATH, this issue is bypassed. > > Are these issues known? Are a number of LD_LIBRARY_PATH using users > using old libperl without knowing it? Should they? Etc. > > Regards, > > -- > Anders. > _______________________________________________ > freebsd-perl@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-perl > To unsubscribe, send any mail to "freebsd-perl-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040718180520.C97857>