BrowserUk has asked for the wisdom of the Perl Monks concerning the following question:

In what format do I have to specify the path in order for EU::MM to be convinced I know what I'm talking about? 

C:\Perl64\packages\DBD-Pg-2.11.8>makefile
Configuring DBD::Pg 2.11.8
Path to pg_config? "C:\Program Files (x86)\PostgreSQL\8.3\bin\"
Not an executable: '"C:\Program Files (x86)\PostgreSQL\8.3\bin\"'
Path to pg_config? "C:\Program Files (x86)\PostgreSQL\8.3\bin\pg_confi
+g.exe"
Not an executable: '"C:\Program Files (x86)\PostgreSQL\8.3\bin\pg_conf
+ig.exe"'
Path to pg_config? "C:/Program Files (x86)/PostgreSQL/8.3/bin/pg_confi
+g.exe"
Not an executable: '"C:/Program Files (x86)/PostgreSQL/8.3/bin/pg_conf
+ig.exe"'
Path to pg_config?

[download]

Ancilliary question: How can I stop EU::MM using Term::Readline?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re: EU::MM (again)
by ikegami (Patriarch) on Apr 15, 2009 at 06:29 UTC
    Note the doubled quotes in the error message. It seems to indicate your quotes are being used as part of the file name. Remove them.
[reply]
Re: EU::MM (again)
by Porculus (Hermit) on Apr 15, 2009 at 08:19 UTC

    Use the source, BrowserUke!

    Ten minutes' post-breakfast browsing reveals that the problems you're having appear to be with App::Info, not EU::MM. And AFAICT neither it, nor EU::MM, nor DBD::Pg's Makefile.PL uses Term::ReadLine at all; the prompting seems to be handled by App::Info::Handler::Prompt, which just does a straightforward <STDIN>.

[reply]
[d/l]
      Use the source ... App::Info::Handler::Prompt, which just does a straightforward <STDIN>.

      Hm. Can that be so? Given that if a simple <STDIN> is used, I get the full power of cmd.exe's command line editing--history etc.--but none of that seems to be available for that (or any other) makefile prompt?

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        http://cpansearch.perl.org/src/MSCHWERN/ExtUtils-MakeMaker-6.50/lib/ExtUtils/MakeMaker.pm 
        sub prompt ($;$) {  ## no critic
    my($mess, $def) = @_;
    Carp::confess("prompt function called without an argument") 
        unless defined $mess;

    my $isa_tty = -t STDIN && (-t STDOUT || !(-f STDOUT || -c STDOUT))
+ ;

    my $dispdef = defined $def ? "[$def] " : " ";
    $def = defined $def ? $def : "";

    local $|=1;
    local $\;
    print "$mess $dispdef";

    my $ans;
    if ($ENV{PERL_MM_USE_DEFAULT} || (!$isa_tty && eof STDIN)) {
        print "$def\n";
    }
    else {
        $ans = <STDIN>;
        if( defined $ans ) {
            chomp $ans;
        }
        else { # user hit ctrl-D
            print "\n";
        }
    }

    return (!defined $ans || $ans eq '') ? $def : $ans;
}

        [download]
        Simple test, each exe appears to get its own history 
        perl -e"warn scalar readline(STDIN)"
perl5.8.7 -e"warn scalar readline(STDIN)"

        [download]
[reply]
[d/l]
[select]
        Why do you expect to get the cmd.exe's features if it isn't cmd.exe that processes your input, but App::Info::Handler::Prompt?
[reply]

Back to Seekers of Perl Wisdom