in reply to Re^2: Perlbrew installing perl failed
in thread Perlbrew installing perl failed

To change from one version of perl to another, you generally just need to modify $PATH.
You can use perlbrew if you wish ... or you could alter $PATH from the command line ... or you could run a script that effects the required change.
I choose the last of those options and have not yet investigated the perlbrew approach. (Given that I'm satisfied with my chosen approach, it's unlikely that I will ever play with perlbrew.)

In addition to AM's comments, it occurs to me that your problem might be unrelated to perlbrew.
The problem you've struck seems to be a fairly rare one. Googling for "recipe for target 'test harness' failed" throws up only this thread.
As AM noted, we really need a bit more information about the error.
Could you give us some context by providing a few of the lines that precede the one you quoted in your original post ?
Also, which version of perl are you trying to install, and what operating system are you using ?
Do you know what "configure" command perlbrew ran ?


Cheers,
Rob

Replies are listed 'Best First'.
Re^4: Perlbrew installing perl failed
by CountZero (Bishop) on May 17, 2015 at 17:05 UTC
    To change from one version of perl to another, you generally just need to modify $PATH.
    And if you forget to reset $PATH to its original value, it is likely you have just messed up the link to your system Perl which can cause all kind of weird problems down the road.

    CountZero

    A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

    My blog: Imperial Deltronics
[reply]
[d/l]
      There's no need to restore $PATH to its original value - unless I've been so insane as to make persistent (so-called "permanent") modifications to it.
      And I'm not that insane.
      I have never messed up the link to my system perl.

      My mind boggles at how feeble-minded I would have to be in order to suffer the consequences you describe.

      Cheers,
      Rob
[reply]
        Interesting.

        So you change $PATH and then run your "other" Perl. Will the $PATH automagically reset once your "other Perl" script starts or finishes? What if meanwhile some other (automatic) script wants to start Perl?

        CountZero

        A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

        My blog: Imperial Deltronics
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom