[Module::Build] Re: [Module-build-general] Module::Build tests failing on new perl 5.8.1

[Bart P. <ba...@la...>]

On Fri, 10 Oct 2003, Ken Williams wrote:

> On Monday, September 29, 2003, at 02:50  PM, Bart Parliman wrote:
> > I noticed that it's using the literal "$(PERL_INC)/perl.exp" and
> > "$(BASEEXT).exp" strings during the 'ld' rather than
> > interpolating them.
> >
> > At first I thought that I had built perl incorrectly, since these
> > literal values are in the "perl -V" output for lddlflags (see
> > below).  After looking at the vendor's built-in perl on a
> > different machine (5.6.0), it appears that 'lddlflags' has these
> > two values in there as well.
>
> Yeah, I wasn't aware that it was legal to have $(VARIABLE)
> interpolation in these Config.pm strings. =(  Is this typical?  Do
> other platforms do this too?  How do those variables get set?

I have access to Linux and Solaris, but don't see anything
similar there.  I guess this doesn't surprise me for AIX, it has
had a checkered history wrt dynamic loading.

The variables appear to be set in perl's own generated Makefiles.
I'm not sure if it actually makes sense to put them in lddlflags
(i.e. perhaps this is a bug in the way perl builds on AIX).  I
just don't know enough about how these config strings are used.

> Since Module::Build uses the multi-argument form of system(), it
> doesn't run any of the arguments through the shell.  This is much safer
> in terms of security and preventing accidents, so I'm not terribly
> excited about changing it.

I understand your reluctance, though if you can fix this it would
be greatly appreciated.  (Several CPAN modules I need now require
Module::Build.)  If this is a general perl build bug, I'm not
sure who to talk to about it.  If you have ideas, please let me
know.

Thanks,

Bart