Problems linking static glib2.0

Jameson Merkow jmerkow at
Tue Oct 7 10:34:25 PDT 2014

So the solution would be to put the macports lib directory at the beginning
of my path when building? Is there a different or better way?


On Tue, Oct 7, 2014 at 10:28 AM, Brandon Allbery <allbery.b at>

> On Tue, Oct 7, 2014 at 1:23 PM, Jameson Merkow <jmerkow at> wrote:
>> I've been using macports for a while. I've been using apple-gcc42
>> compiler, but I recently switched to mp-gcc46, to use mpich-gcc46.  Now
>> that I've switched, Im running into link errors (attached) with the
>> installed glib2.0.  I am linking against the archive, not the dylib (this
>> was working with apple-gcc42). I've tried installing and reinstalling it a
>> few times, to no avail, perhaps I am missing a step?
>> I have the following glib installed:
> It's linking against the system iconv instead of MacPorts' iconv for some
> reason. MacPorts does that because otherwise things link fine and then drop
> core at runtime because the static data is different.
> --
> brandon s allbery kf8nh                               sine nomine
> associates
> allbery.b at
> ballbery at
> unix, openafs, kerberos, infrastructure, xmonad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-users mailing list