Re: [vile] does vile-9.8g require perl newer than perl-5.8.9?

[Gary Jennejohn]

On Sun, 15 Apr 2012 09:09:42 -0400
Thomas Dickey <address@hidden> wrote:

> On Sun, Apr 15, 2012 at 02:54:07PM +0200, Gary Jennejohn wrote:
> > On Sun, 15 Apr 2012 06:55:12 -0400
> > Thomas Dickey <address@hidden> wrote:
> > 
> > > On Sun, Apr 15, 2012 at 11:38:43AM +0200, Gary Jennejohn wrote:
> > > > So, I'm finally getting around to updating the FreeBSD ports to
> > > > vile-9.8g after a long hiatus.
> > > > 
> > > > I had perl-5.8.9 installed and noticed that I couldn't enable perl
> > > > with this version because some perl functionality was missing during
> > > > the processing of perl.xs.  Don't remember all the gory details.
> > > > 
> > > > After installing perl-5.12.4 it all worked.
> > > > 
> > > > So... does vile now require a newer version of perl or was it just a
> > > > problem with a missing perl-5.8.9 package?
> > > 
> > > It sounds like some missing dependency.  Looking at my logs (at machines
> > > I've built on during the past year, and which I could use for testing),
> > > I see that I've been able to build using 5.005003, 5.6.1, 5.8.4, 5.8.5, 
> > > 5.8.9
> > > as well as 5.12
> > > 
> > > The most recent version appears to be 5.14
> > > 
> > > Aside from some work a couple of years ago to accommodate different
> > > versions of perl, I don't recall modifying anything that would affect
> > > its dependencies.
> > > 
> > > Usually the missing piece is the perl development library, which has 
> > > different
> > > names on every system.  For example I have this on Debian 5.0:
> > > 
> > > ii  libperl-dev                                              
> > > 5.10.0-19lenny5                      Perl library: development files
> > > 
> > > The configure script makes a test-compile with a fragment that exercises
> > > the usual problem areas.  Details would show up in config.log
> > >
> > 
> > Here is the error output.  I see no errors in config.log relative to perl, 
> > although there are lots of lines
> > there.  With perl-5.12.4 the missing subroutine seems to be installed as 
> > part of the port, but not with
> > 5.8.9.  Might have to add a warning to UPDATING for the vile/xvile ports.
> > 
> > ===>  Building for vile-9.8g
> > cc -I. -I.  -DHAVE_CONFIG_H   -D_BSD_TYPES -D__BSD_VISIBLE 
> > -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600  
> > -DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.9/BSDPAN" -DHAS_FPSETMASK 
> > -DHAS_FLOATINGPOINT_H -I/usr/local/include 
> > -I/usr/local/lib/perl5/5.8.9/mach/CORE -O2 -pipe -fno-strict-aliasing  
> > -fno-strict-aliasing -pipe  -rpath /usr/local/lib  -o ./mktbls  ./mktbls.c
> > perl /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp  -typemap 
> > /usr/local/lib/perl5/5.8.9/ExtUtils/typemap  -typemap ptypemap  ./perl.xs > 
> > perl.c
> > Undefined subroutine &ExtUtils::ParseXS::errors called at 
> > /usr/local/lib/perl5/5.8.9/ExtUtils/xsubpp line 41.
> 
> I see.  That looks familiar (was probably something that I had to add
> in one or more platforms - rpms seem to be where this was needed).
> In some cases, package dependencies would pull it in automatically...
> 
> On Debian 5.0, that's found here:
> 
> perl-modules: /usr/share/perl/5.10.0/ExtUtils/ParseXS.pm
> 

But that is a more recent perl version.  I suspect that the FreeBSD
perl5.8.9 port is pulling in an older version of ExtUtils, which is part
of the port and not an extra dependency.  Yes, looks like it's grabbing
a BSDPAN tarball from 2009 whereas perl5.12.4 uses one from late 2011.

OK, nothing to be done about it.  No need to pursue this further.

-- 
Gary Jennejohn