On Tue, Jan 8, 2013 at 11:41 PM, Pete Goodeve <pete.goodeve@xxxxxxxxxxxx> wrote: > Oh, yes. The whole app needs to be built under gcc4, and everything > works fine, except this bit. (I think this is the only module that references > stdc++, because it has to work with SWIG. Most of the rest of the suite > is plain C (with occasional C++ internally), and has no trouble. For > instance there are opcodes (csound statements) to *invoke* Python > code, and these work as they're supposed to.) Are you also using a gcc4 python package? The library search paths are set by the runtime loader, and to my knowledge mix and matching compilers within the same app is not supported. Regards, Rene