in reply to Re^2: XML::LibXML::Common 0.13 on linux - undefined symbol
in thread XML::LibXML::Common 0.13 on linux - undefined symbol

gcc will happily use either a static (.a) or a shared lib (.so)

Yes - thanks for correcting that. (On Win32, gcc is also capable of linking to the dll.)
One difficulty in trying to solve the op's problem is that I don't know the name of the file that needs to be linked in. The point I was trying to make was that, if the linking to that file is achieved with '-lxml2', then the linking won't take place, simply because MakeMaker has removed that '-lxml2' link.

Cheers,
Rob
  • Comment on Re^3: XML::LibXML::Common 0.13 on linux - undefined symbol

Replies are listed 'Best First'.
Re^4: XML::LibXML::Common 0.13 on linux - undefined symbol
by almut (Canon) on May 13, 2009 at 00:47 UTC
    ..then the linking won't take place, simply because MakeMaker has removed that '-lxml2' link.

    That's absolutely correct, and I wasn't questioning that  (I was just commenting on your focus on the .a file :)

    As to the contradicting Makefile.PL messages (the have_library() routine obviously did find it!), I think it would be best if the OP simply looked at which commands are actually being run by the Makefile, in order to figure out whether the -lxml2 together with an appropriate -L/... is there on the command line, as it should.