On Fri, 2008-02-01 at 17:58 +0200, Bernd Jendrissek wrote: > On Feb 1, 2008 5:02 PM, Peter Clifton <[EMAIL PROTECTED]> wrote: > > ./gschem: symbol lookup error: ./gschem: undefined symbol: libgeda_factory > > > > I've confirmed that libgeda build OK, and installed, and that ldd shows > > the correct libgeda being found. > > > > grep "libgeda_factory" on that library also returns a match. > > > > Any ideas? > > Ugh. How about "nm $prefix/lib/libgeda.so |grep libgeda_factory"? I get a > 'D' > definition in libgeda, and a 'B' reference in gschem and have no > problems starting > gschem from the build directory. I'll log onto #geda later tonight (when > power > cuts are less likely :) if you want to go through this there.
I've fixed it, you're version has an older soversion (32.0.0) than one of the development releases, which was 32.0.1, so the symlink for libgeda.so.32 was wrong. > Thanks for trying... I've been feeling bad for not looking at this more thoroughly yet, as I want to understand how it works to _use_ before I make any more comments about where we should go with the code, how any features from this can be merged into gEDA. UUIDs or instance naming seems a major point which is likely to be controversial - but I do think we need "something" along these lines. Observers are going to be more and more important, although I wasn't as convinced about the libgeda_factory. I've not dug at it enough recently to make any really informed comments though. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
