On Sun, Aug 8, 2010 at 7:59 AM, Geoff King <gsking1@xxxxxxxxx> wrote: > I tried the source version of your 1.0.2 mudita release. I'm having > problem with the build step. This is with FC13. Any thoughts? >... > -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 > -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype > -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 > -lasound > /usr/bin/ld: levelmeters.o: undefined reference to symbol 'log10@@GLIBC_2.0' > /usr/bin/ld: note: 'log10@@GLIBC_2.0' is defined in DSO /lib/libm.so.6 Geoff -- thanks for reporting this issue. It is a configuration mistake in this release which doesn't show up in F12, which is what I'm still using. Apparently, Fedora13 wants it to link with "-lm", but F12 links happily without "-lm" ...So I never saw this misconfiguration when I tested my distro build on F12... As a quick fix, you should be able to link successfully by adding "-lm" to the end of the linking command: gcc -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/alsa -g -O2 -o envy24control envy24control.o levelmeters.o midi.o mixer.o patchbay.o hardware.o driverevents.o volume.o profiles.o config.o -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lasound -lm The correct approach is to add "-lm" to the configuration files (i thought i had, but mistakenly modified the generated file rather than the configuration input files -- and "make dist-gzip" didn't of course include my modification) ... I will need to fix this build-blunder in the next release. Sorry. If anybody has a suggestion on the most portable/reliable way of doing this, please let me know. I believe adding a line to configure.in-gtk2 like ENVY24CONTROL_LIBS="$LIBS $ALSA_LIBS $GTK_LIBS -lm" would do the trick, but you never know what happens to a simple line of script out in the wild :-). Is the above an accepted&proper way of adding "-lm" to an autoconf file? -- Niels http://nielsmayer.com ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
