Build fails with: gmake[3]: Entering directory `/scratch/chat/telepathy-glib/work/telepathy-glib-0.7.33/telepathy-glib' link -dump -symbols .libs/libtelepathy-glib-internal.a > _gen/abi.nm usage: link file1 file2 It seems NM is wrongly defined: ac_cv_prog_NM='link -dump -symbols' configure says: checking for nm... link -dump -symbols I don't know why it gets that idea. I can override it by giving "NM=nm" as configure argument.
This looks like a problem with libtool (whose detection of nm we're using); sorry, someone who uses NetBSD will have to debug this. The relevant section of config.log might have useful information as to why libtool's code doesn't like your nm implementation.
Is this reproducible? What does config.log say? How does libtool normally list symbols (e.g. for the -export-symbols-regex feature) under NetBSD?
I've just tried again with 0.11.11 (I know, not the latest), and it seems the problem is fixed: configure:4885: checking for BSD- or MS-compatible name lister (nm) configure:4934: result: /usr/bin/nm -B configure:5052: checking the name lister (/usr/bin/nm -B) interface configure:5059: cc -std=gnu99 -c -O2 -I/usr/pkg/include -I/usr/include -I/usr/pk g/include/python2.6 -I/usr/X11R7/include -I/usr/pkg/include -I/usr/include -I/us r/pkg/include/python2.6 -I/usr/X11R7/include conftest.c >&5 configure:5062: /usr/bin/nm -B "conftest.o" configure:5065: output 0000000000000000 B some_variable configure:5072: result: BSD nm ... configure:12677: checking for nm configure:12704: result: /usr/bin/nm -B ... ac_cv_prog_NM='/usr/bin/nm -B' Thanks to whoever fixed it in the meantime!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.