> Another workaround could be: (1) don't use libcryptopp.a, and (2) use > >> libcryptopp.so. > > > Tried that. Didn't help. >
That's a drag. I thought you might be compiling against one vrsion, and then runtime linking against another version. > Can you get me remote access to that machine? >> > > No. It does not belong to me, it belongs to my client. > > Can you bring me on as a subcontractor? Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
