[sldev] GTK 2.8

[Jesse Armand]

Well, I have tried the quick fix that you mentioned, in both of these
group of lines:

    if test "$GCC_USE_GNU_LD"; then
        # Don't allow undefined symbols in libraries
       DSO_LDOPTS="$DSO_LDOPTS -Wl,-z,defs"
    fi

    if test "$GNU_LD"; then
        # Don't allow undefined symbols in libraries
        DSO_LDOPTS="$DSO_LDOPTS -z defs"
    fi

I've tried to comment it, and it doesn't work.

Is there any other way to handle this ?

On Sat, Mar 22, 2008 at 8:44 AM, Carsten Juttner <carjay at gmx.net> wrote:
>
>  I had the same problem, it's not related to GTK, the newer mozilla build
>  process simply added a new linker flag that demands that all symbols
>  have to be resolved for object files at link time.
>
>  Ft_MulFix and the other unresolved symbols are part of the
>  freetype2-library but the mozilla build does not add it to the link line
>  probably because the mozilla guys believed that the linker flags derived
>  from the pkg-config reply for Xft would already include the freetype
>  library.
>
>  But for my distro (Kubuntu Feisty) this is not the case, obviously
>  because you don't need to call the freetype API when using the Xft API
>  so the usage of freetype is private to Xft.
>
>  For a quick fix try to remove the "DSO_LDOPTS ="$DSO_LDOPTS -Wl,-z,defs"
>  lines from configure.in
>
>  Regards,
>  Carsten
>
>
>
>  _______________________________________________
>  Click here to unsubscribe or manage your list subscription:
>  /index.html
>