On Fri, Oct 2, 2009 at 1:29 AM, Phil Blundell <ph...@gnu.org> wrote: > On Thu, 2009-10-01 at 19:58 -0700, ed wrote: >> I get this message in the log. >> >> NOTE: Running task 40 of 2678 (ID: >> 1757, /home/ed/mini2440/OE/mini2440/recipes/m4/m4-native_1.4.12.bb, >> do_patch) >> NOTE: Running task 41 of 2678 (ID: >> 1758, /home/ed/mini2440/OE/mini2440/recipes/m4/m4-native_1.4.12.bb, >> do_configure) >> *** %n in writable segment detected *** >> >> Is this something to be concerned about? > > Not unduly. It's caused by a bug in one of the test programs that m4's > configure script runs, which is tripping a security check in glibc. The > program in question will be aborted, which could be causing autoconf to > get the wrong result for one of its tests, so the error isn't entirely > harmless, but if the resulting m4 seems to be working ok then it is > probably no cause for serious alarm.
yes for me m4 worked fine and that was my assumption. > > p. > > > > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
