Re: Module::Build can't locate the perl binary

Hi, I had the same problem (btw. very annoying problem). After analisys of this #$%^&*!!! and test ALL posibilities checked in magic sub "find_perl_interpretter" to find /usr/bin/perl I decided to insert 1 simple line at the begining of this sub:
return "/usr/bin/perl";
After then I just ignore funny warning "* WARNING: Configuration was initially created with '/usr/bin/perl', but we are now using '/usr/bin/perl'." because of its stupidity. Works wonderfully.

!!!Note: if you don't know wher is your perl do not try do this!!!

Comment on Re: Module::Build can't locate the perl binary Download Code

Replies are listed 'Best First'.
Re^2: Module::Build can't locate the perl binary (qx, UTF?) by tye (Sage) on Jun 16, 2007 at 02:36 UTC
Elementary debugging skills tell me that the problem is then with the few-line sub _perl_is_same. Which means that the string from Config->myconfig() isn't `eq` when dragged through print and qx. Given that this is a little-seen problem and involves RedHat, my first guess would be a UTF problem. But I'm sure Ken would appreciate someone who has this distribution getting a dump of the two versions of the string involed. I'd find that trivial to do with the Perl debugger but one could also just insert some `warn Dump Config->myconfig()` or such code. (I don't have RedHat handy.) - tye	[reply] [d/l] [select]
Re^2: Module::Build can't locate the perl binary by shenme (Priest) on Nov 30, 2006 at 22:18 UTC
Ya'know, I just can't help but wonder if this has any relation to the subject of (OT) Fixing Line Endings? If the perl binary value _was_ picked up from a #! line, could that line have been 'corrupted' similarly?	[reply]