in reply to How to get Ext::Liblist to recognise different library paths?

hmm, what point does it fail / how far does it get?

Have you tried fudging the install by inserting the path of libexpat.so into your PATH environment variable?

or adding a begin block at the very top of the build script?

eg. 
BEGIN {
    my $custom_lib_path = './blah/blah/etc';
    push @INC, $custom_lib_path;
}

[download]

Replies are listed 'Best First'.
Re^2: How to get Ext::Liblist to recognise different library paths?
by Fairchild (Acolyte) on Dec 10, 2009 at 10:32 UTC
    Hi,

    It fails at the starting point. That is, perl Makefile.PL. It barfs becauses it cant locate libexpat.so. If Ext::Liblist followed LD_LIBRARY_PATH then it would see it.

    The suggestion about using a soft link would probably solve the problem but I dont have root on that particular machine.

    I was aware about the suggestion about using the environment variable EXT... although the same documentation indicated that using LD_LIBRARY_PATH could resolve the problem as well.

    I did read the various documentation, searched the web, tried setting various environment variables on different platforms, etc.

    In summary, if there is no other way then I will use the environment variable mentioned above. I guess I am just abit surprised that something like Ext::Liblist isnt very flexible (i.e. can't search LD_LIBRARY_PATH or a similar type of environment variable) - since it's such a standard package of perl and perl being a very flexible swiss army knife.

    Fairchild.
[reply]

In Section Seekers of Perl Wisdom