Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re^2: Architecture-specific module conflicts under perlbrew

by gnosti (Friar)
on May 16, 2013 at 19:14 UTC ( #1033893=note: print w/ replies, xml ) Need Help??


in reply to Re: Architecture-specific module conflicts under perlbrew
in thread Architecture-specific module conflicts under perlbrew

Yes, XS.pm got installed to the wrong directory in my @INC, an arch-specific but perl version-agnostic directory that should not even exist!

You're right about opening an issue, although the previous reply suggests I might be able to get the correct behavior by setting the appropriate environment variables.

Usually I come to PM first with my problems because they are more often due to my own ignorance than to a bug.

Thanks and good luck with your various boxen.


Comment on Re^2: Architecture-specific module conflicts under perlbrew
Re^3: Architecture-specific module conflicts under perlbrew
by karlgoethebier (Vicar) on May 16, 2013 at 21:15 UTC
    «Yes, XS.pm got installed to the wrong directory in my @INC...»

    But you don't get this well known message:

    Karls-Mac-mini:~ karl $ perl -MFOO Can't locate FOO.pm in @INC (@INC contains: #...bla, bla

    You get Perl API version v5.14.0...Compilation failed in require.

    That damned thing seems to be available - perhaps a bad place, but it is in your @INC, isn't it?

    Totally stupid "brute force" approach: Copy that thing to a place where you think it belongs (in @INC).

    Do you still get this compile time error? Or do i still miss something?

    Best regards, Karl

    «The Crux of the Biscuit is the Apostrophe»

      I believe that JSON::XS was installed under perl 5.14, and found (and choked on) by a separate perl 5.16. If I install with cpanm -f I can clobber one version with another, but that sort of defeats the purpose of perlbrew, which is separate, functioning alternative perl versions with their respective modules.

      I posted that as an example of things generally going wrong, rather than as a specific glitch to overcome.

      regards,

      Joel

        "I posted that as an example of things generally going wrong, rather than as a specific glitch to overcome."

        This is, cautiously said: a "funny approach". Isn't PM (partly) about "overcoming glitches"?

        When i discovered perlbrew, i thought this is heaven-sent. But i'm skeptical about "this is the promised land" stuff.

        So i installed it on different boxes, played around with it, tried to break it, did some insane things.

        But it didn't break. It worked.

        So i recommended it for a box that is a good part of my job. The box is for monitoring more than 120 hosts with more than 1000 services.

        Setup and testing lasted about 3 month. And many people are relying on this box. And i recommended the tool on PM.

        So, if someone comes and says: "That stuff you recommend doesn't work as expected!" the bells ring.

        I try to understand why and how to find a solution.

        If i where you (assuming you are still interested in using perlbrew) i would throw away that whole stuff and start over again with a fresh setup, doing it exactly as described in the docs.

        If you can reproduce the issue, contact the author. I'm shure you get help - many rely upon perlbrew.

        Best regards, Karl

        P.S.: Ever had a broken Perl? No? So you are lucky. I had it one time on a Mac OS X server.

        I fired up cpan and went for lunch or so.

        When i was back, i had another Perl installed, tons of modules uninstalled and tons of modules new installed.

        The box was unuseable - and it was not for testing purposes.

        «The Crux of the Biscuit is the Apostrophe»

        «...I can clobber one version with another...»

        I hope i got it...

        But as i mentioned, i couldn't reproduce it under Mac OS X Mountain Lion with two different versions of Perl (or i think so).

        Perhaps it would have been better if i had posted some details of my observations.

        Unfortunately i can't access this box on weekend.

        But i can do this next week, when back in office.

        And i installed another Perl version on my box at home (Lion). If i find the time i'll give it a try (but i'm not shure if this makes sense).

        I don't have a Linux box for testing this issue but i think this doesn't matter.

        Please note, that i didn't want to be harsh.

        I just want to understand this story and bring it to a good end - if possible.

        Update:

        Sorry, i still didn't find the time to check this, but i'll be back ;-)

        Best regards, Karl

        «The Crux of the Biscuit is the Apostrophe»

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1033893]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (19)
As of 2015-07-02 13:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (39 votes), past polls