Stephen, Have you seen bug 2786023? The python bindings seem unable core libstdc++ symbols. This shouldn't happen - compiling with g++ should automatically link it properly against the appropriate libstdc++, but I don't really understand how the python wrappers find their libraries.
I've tried to reproduce this on two debian boxes and an ubuntu box with no luck. The user can fix it by adding -lstdc++ to the build flags for libconcord, but... that so shouldn't be necessary. Since 'ldd libconcord.so.1' finds it libraries either way, I believe it's working around some oddity in the python bindings build. Can you have a look at this? http://sourceforge.net/tracker/?func=detail&atid=978127&aid=2786023&group_id=201579 At this point the only thing I can think of is ask the user to delete all libconcord/bindings/concordance/congruity files, make sure his system is fully up-to-date, and try rebuilding it all again.... but that kinda sucks. -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
