develooper Front page | perl.perl5.porters | Postings from June 2016

Re: [perl #128451] [Win32]$Config{libpth} is broken in 5.25.2

Thread Next
From:
sisyphus1
Date:
June 28, 2016 01:48
Subject:
Re: [perl #128451] [Win32]$Config{libpth} is broken in 5.25.2
Message ID:
52AB39DE6B494A478157463F5C805E69@OwnerPC311012

-----Original Message----- 
From: bulk88 via RT
Sent: Tuesday, June 28, 2016 6:53 AM
To: sisyphus1@optusnet.com.au
Subject: [perl #128451] [Win32]$Config{libpth} is broken in 5.25.2

> On Tue Jun 21 19:14:39 2016, sisyphus wrote:
>> Hi,
>>
>> The problem is that $Config{libpth} places whatever is specified in
>> EXTRALIBDIRS (in GNUmakefile) inside double quotes:
>
> related bug https://rt.perl.org/Ticket/Display.html?id=123575

I don't see the relationship ... though please don't think that I'm 
asserting there isn't one.

When I diff the GNUmakefile that shipped with 5.24.0 against the GNUmakefile 
that ships with 5.25.2, the only differences that are presented are:

1) differences in version number (ie 5.24.0 has become 5.25.2, 524 has 
become 525 and 5240 has become 5252);
2) the inclusion in 5.25.2 of the line:
    -if exist $(LIBDIR)\Test2 rmdir /s /q $(LIBDIR)\Test

Incidentally, I would have expected that should be:
    -if exist $(LIBDIR)\Test2 rmdir /s /q $(LIBDIR)\Test2

I don't see anything that would be involved in the change of behaviour (from 
5.24.0 to 5.25.2) re the setting of $Config{libpth}.

Just to be sure that the problem is expressed clearly:
If, in GNUmakefile I change the (empty) EXTRALIBDIRS spec to:

EXTRALIBDIRS    := C:\foo C:\bar

then in 5.24.0, $Config{libpth} will be set to
C:\wherever\lib C:\foo C:\bar

and that's fine. But in 5.25.2, $Config{libpth} will be set to
C:\wherever\lib "C:\foo C:\bar"

thus ensuring that  any lib in C:\foo or C:\bar will not be located.

Cheers,
Rob 


Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About