in reply to Re^2: FindBin works different on Fedora Core 2?
in thread FindBin works differently on Fedora Core 2?

I dug a little deeper -- short anwer is that it's not FindBin, but Cwd.

The difference seems to be when FindBin calls Cwd::abs_path(). With an argument as simple as '/tmp/', the older version (2.06 in my case) of Cwd::abs_path will chop the trailing slash, whereas the newer version from FC2 will not (Cwd version 2.12).

So the culprit is Cwd rather than FindBin. I'll leave it to you to find the specific difference in the abs_path behavior (I think you'll see what I mean once you start digging).

Do tell us what you find out.

Matt

  • Comment on Re^3: FindBin works different on Fedora Core 2?

Replies are listed 'Best First'.
Re^4: FindBin works different on Fedora Core 2?
by samtregar (Abbot) on Jun 08, 2004 at 01:51 UTC
    Another excellent theory, but it's not correct either. Both my Fedora Core 1 system and Fedora Core 2 system have the same version of Cwd: 2.12. That's the version that ships with Perl 5.8.3 and they both have 5.8.3 installed. As far as I can tell they have the exact same version of all the relevent Perl modules...

    -sam

[reply]
      Let's nail down some variables, here.

      So far, I know two things -- one, you see the described behavior on your installations of FC1 and FC2. Two, I can reproduce the behavior on pre-FC1 (Shrike -- RH 9) and FC2. Looking at the module progressions -- not merely the perl progressions -- I can see many potentially relevant changes within the modules involved.

      So. Let's nail down what code is running in each of your instances. It's perl 5.8.3 in both cases, as you say -- just to be sure, let's verify that. Ensure that each executable is the version you think it is.

      Second, check your %INC hash. There could be local versions of these modules that are of a different version than the default shipped with perl 5.8.3.

      Third -- and this is not likely but possible -- check that your perls are actually using version numbering on their system library directories (which should be the case by default, and should be the case with FC*, but if you've been doing regular package updates on them you will notice different perl version numbers down in /usr/lib/perl5). In any case, ensuring the perl executable version and the contents of %INC will flush this out as well.

      If none of these appear to be running the newer code, which we know to exhibit the behavior you describe (as opposed to an earlier version of FC1 with no package updates, perhaps, but certainly the version of redhat just prior to FC1), then I will join you in being stumped.

      Cheers,
      Matt

[reply]
        It's perl 5.8.3 in both cases, as you say -- just to be sure, let's verify that. Ensure that each executable is the version you think it is

        Verified. Both return 5.8.3 from 'perl -v'. However, the one on Fedora2 was built for i386-linux-thread-multi and the one on Fedora1 was build for i686-linux. I don't know why that would effect FindBin...

        Second, check your %INC hash.

        Done. Both %INC hashes are identical. Both scripts load the same modules from the same places, all within the 5.8.3 base module tree.

        Third -- and this is not likely but possible -- check that your perls are actually using version numbering on their system library directories

        Checked. Both are using 5.8.3 in their module paths.

        then I will join you in being stumped.

        Welcome to the club. I guess I'll just fix it and move on... I've got a nasty seg-fault to track down anyway.

        -sam

[reply]

In Section Seekers of Perl Wisdom