MFerenc's solution works for me, thank you. It seems like MacPorts' team is working on this issue. It might be fixed in the next version of 2.6.4.