Hi Paul, >> utilities.c:35:22: fatal error: execinfo.h: No such file or directory >> compilation terminated. >> make[3]: *** [utilities.lo] Error 1 >> make[3]: Leaving directory >> `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/libfsobasics-1_0.9.10+gitr0+b163e36f9c960c6fea92168e88201be98dcceaef-r2.0/git/libfsobasics/fsobasics' >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory >> `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/libfsobasics-1_0.9.10+gitr0+b163e36f9c960c6fea92168e88201be98dcceaef-r2.0/git/libfsobasics/fsobasics' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory >> `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/libfsobasics-1_0.9.10+gitr0+b163e36f9c960c6fea92168e88201be98dcceaef-r2.0/git/libfsobasics' >> make: *** [all] Error 2 >> FATAL: oe_runmake failed >> ERROR: Function do_compile failed >> >> Does anyone have a clue on how that can be fixed. > > `execinfo.h` is not available in uClibc and is a “GNUism” [2]. The > dependency in in `linux.vapi` [3] and got included in [4]. > > Unfortunately I do not know how to exclude that. I guess Autotools > should check if `execinfo.h` is available and only use it if it is. But > I do not know how to do that. Michael, are those libraries intended to > be used with uClibc?
Yeah. I'll think about a way to fix it when I'm back end of next week (currently on vacation). > If this is too much work, how can I exclude this recipe from > console-image for minimal-uclibc? I bet there are some of my debugging utilities dragging this in, check – and remove for now – these. Cheers, :M: _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
