Somebody claiming to be Antoine Jacoutot wrote:
> I think this is less of a hammer:
I went with the bigger hammer to make sure all of the configure overrides
would get through and not just the one that was observed causing problems
when it got lost. But I don't have strong feelings about which side of
that tradeoff is the correct one to take.
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/devel/arm-none-eabi/newlib/Makefile,v
> retrieving revision 1.1.1.1
> diff -u -p -u -p -r1.1.1.1 Makefile
> --- Makefile 28 May 2015 23:28:26 -0000 1.1.1.1
> +++ Makefile 13 Jul 2015 16:33:26 -0000
> @@ -25,6 +25,13 @@ USE_GROFF= No
> CONFIGURE_ARGS+=--enable-interwork \
> --enable-multilib
>
> +# The build stage for newlib invokes configure (repeatedly), so make
> +# sure the sub-configures run in a suitable environment.
> +# Without this, if coreutils is present at configure time, the
> +# sub-configures will pick up gmkdir as their preferred concurrency-safe
> +# 'mkdir -p'
> +MAKE_ENV += MKDIR_P='mkdir -p'
> +
> post-install:
> ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/newlib
> ${INSTALL_DATA} ${WRKDIST}/COPYING.NEWLIB \
>
>
--
Dave Vandervies
dj3va...@terse.ca / dj3va...@uwaterloo.ca
Plan your future! Make God laugh!
