[lxml-dev] Fwd: Re: lxml Mac installation idea

[Michael Guntsche]

CC'ing lxml-dev

-------- Original Message --------
Subject: Re: [lxml-dev] lxml Mac installation idea
Date: Sun, 9 Nov 2008 23:12:32 +0100
From: Guntsche Michael <mike at it-loops.com>
To: Stefan Behnel <stefan_ml at behnel.de>


On Nov 9, 2008, at 22:59, Stefan Behnel wrote:

> Hi,
>
>
> On a normal system, that shouldn't pose a problem at all. But if  
> lxml.etree
> reports that the runtime linker linked it with the correct, up-to-date
> library, and then it crashes due to a problem in the outdated system  
> library,
> which should not even have been loaded, I just can't call that the  
> normal
> behaviour of an "operating" system.
>

I never said that MacosX is normal. :)
It is really botched in some places, especially in the library  
department.

> So you mean that you are building lxml manually and you do not use the
> macports build, right? Is there anything you have to do at runtime,  
> or does it
> "just work" for you once it's built and installed?


Exactly.
I just made sure that every related library that comes from macports,  
in this case libxml, libexslt and libiconv are build as universal  
binary.
The latest builds I have are running through a "make test" without any  
problems. They even survive the test-suite you posted a few months ago.
I still do not understand why the linker picks up the internal  
libraries during runtime. Maybe if someone with a "broken" setup could  
give me more information about it (universal binaries, self-compiled  
from macports etc..) I can figure out what's going on.

Kind regards,
Michael