On 3/20/07, Martin Costabel <[EMAIL PROTECTED]> wrote:
> Chris Wolf wrote:
> > On 3/19/07, Alexander K. Hansen <[EMAIL PROTECTED]> wrote:
> >> Chris Wolf wrote:
> []
> >>> dyld: Library not loaded: /sw/lib/libgobject-2.0.0.dylib
> >>>   Referenced from:
> >>> /sw/src/fink.build/pango1-xft2-1.10.1-1003/pango-1.10.1/pango/.libs/pango-querymodules
> >>>   Reason: Incompatible library version: pango-querymodules requires
> >>> version 1201.0.0 or later, but libgobject-2.0.0.dylib provides version
> >>> 401.0.0
> >>> [...]
> >>> Failed: phase compiling: pango1-xft2-1.10.1-1003 failed
>
> This is very strange. Your "pango-querymodules" executable that was just
> being compiled, saw a libgobject-2.0.0.dylib with compatibility version
> 1201.0.0 when it was compiled, but now, when it is being used - probably
> just second after it was compiled - it sees an older version with
> compatibility version 401.0.0.
>
> The only scenario I can imagine that can have this result is that you
> have somehow been mixing things from the stable and unstable trees, and
> now your various libgobject-*.dylib files are in an inconsistent state.
> Please look at
>
>     ls -l /sw/lib/libgobject*b
>
> or perhaps better
>
>    file /sw/lib/libgobject*b
>
> In my case I get
>
> /sw/lib/libgobject-2.0.0.1200.11.dylib: Mach-O dynamically linked shared
> library i386
> /sw/lib/libgobject-2.0.0.dylib:     symbolic link to
> `libgobject-2.0.0.1200.11.dylib'
> /sw/lib/libgobject-2.0.dylib:       symbolic link to
> `libgobject-2.0.0.1200.11.dylib'
>
> The important thing is that both libgobject-2.0.dylib (compile time
> object) and libgobject-2.0.0.dylib (runtime object) point to the same
> file. I bet that this is not the case for you.
>
> []
> > I had already done that and should have mentioned that fink shows
> > glib2-shlibs-2.12.0-103 as the current version.  Thanks...
>
> This means that you do not have the unstable tree activated, right?
>
> --
> Martin
>
>
Martin, thanks for your help, which explains the issue -- I seem to have *both*
versions:

s -l libgobject-2.0.*
-rwxr-xr-x   1 root  admin  278352 Mar 18 01:50 libgobject-2.0.0.1200.0.dylib
-rwxr-xr-x   1 root  admin  287884 Mar 18 07:36 libgobject-2.0.0.400.8.dylib
lrwxr-xr-x   1 root  admin      28 Mar 18 07:36 libgobject-2.0.0.dylib
-> libgobject-2.0.0.400.8.dylib
-rw-r--r--   1 root  admin  399844 Mar 18 01:50 libgobject-2.0.a
lrwxr-xr-x   1 root  admin      29 Mar 18 08:02 libgobject-2.0.dylib
-> libgobject-2.0.0.1200.0.dylib
-rwxr-xr-x   1 root  admin     931 Mar 18 01:50 libgobject-2.0.la

...and, yes, I had the unstable tree activiated, per the instructions I was
following here:

http://captnswing.net/2006/07/10/gnucash20_on_intel_macs.html

In the middle of these steps, I kept getting a fink error in on
"unstable/libcrypto...",
so I unconfigured fink to turn off the unstable tree to shut it up.

Maybe these are not the best instructions to follow.  If there is a cleaner
procedure to follow, please advise.  I suspect I will have to blow away /sw
and start from scratch, huh?

Thanks again,

  -Chris

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to