On Wed, 3 Apr 2013, Phil Dibowitz wrote: > Actually, while libconcord builds now, concordance doesn't: > > [phil@rider concordance]$ make > make all-am > make[1]: Entering directory > `/home/phil/build/cvs/concordance_zwave/concordance' > gcc -DHAVE_CONFIG_H -I. -Wall -ansi -pedantic-errors -g -O2 -MT > concordance-concordance.o -MD -MP -MF .deps/concordance-concordance.Tpo -c -o > concordance-concordance.o `test -f 'concordance.c' || echo './'`concordance.c > mv -f .deps/concordance-concordance.Tpo .deps/concordance-concordance.Po > /bin/bash ./libtool --tag=CC --mode=link gcc -Wall -ansi -pedantic-errors -g > -O2 -lconcord -o concordance concordance-concordance.o > libtool: link: gcc -Wall -ansi -pedantic-errors -g -O2 -o concordance > concordance-concordance.o /usr/lib/libconcord.so > /usr/lib/libconcord.so: undefined reference to `vtable for CRemoteMH' > collect2: ld returned 1 exit status > make[1]: *** [concordance] Error 1 > make[1]: Leaving directory > `/home/phil/build/cvs/concordance_zwave/concordance' > make: *** [all] Error 2
Clean checkout and build worked fine for me. Sure you don't need a make clean or something? ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
