On 7/25/07, Stefan Bruda <[EMAIL PROTECTED]> wrote:

>> Err, sorry, I meant the other way around (the upgrade is from
>> 0.3.10_2 to 0.3.12_0).
>
> Then I'm not sure. Perhaps try deactivating the 0.3.10_2 version
> first, then install the 0.3.12_0 version.

Thank you for the suggestion, but I must confess I did not expect it to
work (the problem is undefined symbols during linking) and indeed it does
not.

The same issue is by the way signalled in another recent post
<http://lists.macosforge.org/pipermail/macports-users/2007-July/004616.html>.

Anybody knows at least where are composite_in_* symbold supposed to come
from?

As far as I can tell, the symbols are internal to the package :(

David
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to