[GEM-dev] Problems linking external against latest GEM build

IOhannes m zmoelnig zmoelnig at iem.at
Tue Feb 7 15:38:51 CET 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2012-02-07 15:24, Theo Burt wrote:
> On 07/02/2012 12:59, Theo Burt wrote:
>> Hi, really stuck at the moment... and would really appreciate any help.
>>
>> I'm working in OS X, and I have an external I've been using/updating
>> for years which links against GEM (it uses both CPPExtern and
>> GEMBase). In the version of GEM shipped (precompiled) with PD-Extended
>> (and every other previous version) it works fine, but I can't get it
>> to link with the latest OS X binary for 92.3.
>>
>> It seems to be that my external name-mangles (for example)
>> CPPExtern::post to __ZN9CPPExtern4postEPKcz
>> But browsing the symbols in the new OS X binary, the name has been
>> mangled to      __ZNK9CPPExtern4postEPKcz (note the extra 'K')
>>
>> I just can't find out why this is the case... does anyone have any
>> idea at all? Any help really really appreciated, have been stuck on
>> this for several days!


c++filt helps with resolving name mangling.
the extra 'K' means, that the CPPExtern::post() message is now declared
"const"...

the problem you are experiencing is most likely because you are using
Gem-headers for compilation that do not match the Gem-binary.

fgmadsr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8xN3gACgkQkX2Xpv6ydvQovACgvPv6ydBcqTCIrMFR0PiXnqYc
1YUAn32kdhzFlbHhVC/0M2sfl9+WK9hF
=VLuU
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20120207/807dded8/attachment.bin>


More information about the GEM-dev mailing list