On 9 Apr, 2008, at 2:59, Paul Everitt wrote:
>
> Hi all. I have a weird issue and I'm looking for ideas on how to
> debug it.
>
> I'm using the system Python on Leopard and I'm trying to bundle lxml
> compiled against an update libxml2/libxslt install. I want to use
> py2app to freeze everything into a .app.
>
> For a basic, no-GUI app bundle, everything works fine.
>
> However, when my application uses a WebKit widget, I get a segfault
> when
> doing various lxml operations. A few lines added to the
> PyDocURLProtocol example application demonstrate the problem.
>
> lxml has some constants you can get to and inspect the version of
> libxml
> that lxml is compiled against. When I run my .app, I see the newer
> versions and not the system versions of libxml2/libxslt. Also, I see
> the dylib copied into the bundled.
>
> My suspicion is that, because WebKit has a libxml2 and libxslt, that
> somehow the two are conflicting. But, it's hard to investigate.
>
> Any suggestions?
I have a couple of things you could look into:
- does the application work when you use an alias bundle (py2app -A)?
- is your own build of lxml/libxml/... build using two-level
namespaces or a single-level namespace? The former is default, to get
the second you have to add '-flat_namespace' or '-
force_flat_namespace' to the command-line while linking. The latter
option is especially suspect, as it can cause problems like the one
you're having.
Ronald
>
>
> --Paul
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
|
