On Sun, Jul 12, 2015 at 11:11:09PM +0100, Nigel Taylor wrote: > On 07/12/15 13:27, Antoine Jacoutot wrote: > > In case anyone is interested, devel/arm-none-eabi/newlib broke in my bulk > > because gmkdir was detected at configure time (and junked by dpb later on). > > > > <...> > > checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p > > <...> > > Making install in . > > gmake[3]: Entering directory > > '/exopi-obj/pobj/arm-none-eabi-newlib-2.2.0.1/newlib-2.2.0-1/arm-none-eabi/newlib' > > gmake[4]: Entering directory > > '/exopi-obj/pobj/arm-none-eabi-newlib-2.2.0.1/newlib-2.2.0-1/arm-none-eabi/newlib' > > gmake[4]: Nothing to be done for 'install-exec-am'. > > /usr/local/bin/gmkdir -p > > '/exopi-obj/pobj/arm-none-eabi-newlib-2.2.0.1/fake-amd64/usr/local/arm-none-eabi/lib' > > Makefile:500: recipe for target 'install-toollibLIBRARIES' failed > > /bin/sh: /usr/local/bin/gmkdir: not found > > gmake[4]: Leaving directory > > '/exopi-obj/pobj/arm-none-eabi-newlib-2.2.0.1/newlib-2.2.0-1/arm-none-eabi/newlib' > > gmake[4]: *** [install-toollibLIBRARIES] Error 1 > > > > > > I have absolutely no time to look at this... > > > coreutils contains gmkdir
Yes sure. The real question is why arm-none-eabi-newlib does not pick up our infrastructure override. -- Antoine
