#84 Source -> Format throws error if Perl is at UNC path

open
LeO
Editor (234)
5
2004-10-12
2004-08-10
Leo Sager
No

Using Eclipse 3.0 final version, and Eclipse plugin 0.3.0.
Windows XP platform.

If I define perl to be located at the UNC path
\\server\share\path\to\perl\bin\perl, then when I do
Source -> Format I get a windows pop up box that says

The application or DLL
UNC\server\share\path\to\perl\site\lib\auto\HTML\Parser\ Parser.dll is not a valid window image. Check your
installation diskettes.

After I click OK, then it does seem to format OK.

If I change perl to be defined to a perl that is local to
my system, then no errors come from Source -> Format.

Any ideas?
Could it be the UNC version of Perl is corrupt?
I am not exporting to HTML, so therew's no reason to be
looking at an HTML parser anyways.

Discussion

<< < 1 2 (Page 2 of 2)
  • LeO
    LeO
    2004-10-06

    Logged In: YES
    user_id=703323

    My guess:

    Perl is executed on a (UNC)host. And from this host, where
    Perl is executed, it could not access to your host, namely
    where the Tidy.pm is located. Therefore the question if you
    perform Perl and then make something like Ping to your host
    (or something equivalent) I highly guess, you cannot reach
    your localPC. Only one-way direction.

    I'm not THAT Perl-expert, so I don't know how to make
    something like Ping on THAT UNC-host. That's your task -
    sorry, but have no other options available.

    Other additional question: Is Tidy.pm somewhere found that
    UNC-Host?
    LeO2Leo ;)

     
  • LeO
    LeO
    2004-10-06

    • assigned_to: luelljoc --> leo_forge
     
  • Leo Sager
    Leo Sager
    2004-10-07

    Logged In: YES
    user_id=1100486

    The perl process runs on my local box, not on the host
    machine of the UNC.

    Tidy.pm is only found on my local PC in the installation of the
    plug in, there is no tidy.pm in the perl distribution at the UNC
    path.

    Things *are* getting formatted, so Tidy.pm is running...

     
  • LeO
    LeO
    2004-10-08

    • assigned_to: leo_forge --> luelljoc
     
  • LeO
    LeO
    2004-10-08

    Logged In: YES
    user_id=703323

    HM', perhaps I missunderstand something:

    1) How is it possible that perl runs on your machine, when it is
    installed on the UNC-path? Or does this mean you have also
    local installation? But still, I do not get it, how this local Perl
    could be excecuted, when you specify a remote one.

    2) How do you come to the conclusion of your last paragraph?
    i.e. from where could you detect Tidy.pm was running?

     
  • Leo Sager
    Leo Sager
    2004-10-11

    Logged In: YES
    user_id=1100486

    Perl is installed on some file server (unc path). But when you
    execute it, it doesn't run on that file server, it runs on the
    computer where you are running it from (aka, the perl.exe is
    executing on my local machine).

    By examining the @INC path, I looked for Tidy.pm and only
    the one in the plug in is found.

     
  • LeO
    LeO
    2004-10-12

    Logged In: YES
    user_id=703323

    Hm', I still have my doubts, buttttt.....

    How do you configure the perl Statement in the preferences?
    If I do it like "\\hostname\perldir\perl" I get an Error as
    well if I type it in the DOS-box

    '\\hostname\perldir\perl' is not recognized as an internal
    or external command, operable program or batch file.

    So, what's the magic trick to perform this statement as well
    in the DOS-box?

    BTW: Could you test the following script:

    use Sys::Hostname;
    print hostname();

    Is it the UNC-hostname or your localhost-name???

    LeO

     
  • LeO
    LeO
    2004-10-12

    • assigned_to: luelljoc --> leo_forge
     
  • Leo Sager
    Leo Sager
    2004-10-12

    Logged In: YES
    user_id=1100486

    In the preferences, perl is defined as:

    \\febbos001na\releng\perl\win32\bin\perl.exe

    The hostname prints out as my hostname.

     
  • Jan Ploski
    Jan Ploski
    2006-08-04

    Logged In: YES
    user_id=86907

    Can you reproduce this bug in 0.4.x? If not, I vote for
    closing it as 'Out of Date'.

     
<< < 1 2 (Page 2 of 2)