%% $,1(4(U(Y(b(U(`(B $,1(0([(U(Z(a(P(](T(`(B $,1(2(P([(U(`(X(B
$,1(U(R(X(g(B <[EMAIL PROTECTED]> writes:
n> Makefile:
n> multilib.out: maybe-all-gcc
n> @r=`${PWD_COMMAND}`; export r; \
n> echo "Checking multilib configuration..."; \
n> $(CC_FOR_TARGET) --print-multi-lib > multilib.tmp 2> /dev/null ; \
n> $(SHELL) $(srcdir)/move-if-change multilib.tmp multilib.out ; \
n> after change to:
n> multilib.out: maybe-all-gcc
n> @r=`${PWD_COMMAND}`; export r; \
n> echo "Checking multilib configuration..."; \
n> $(CC_FOR_TARGET) --print-multi-lib > multilib.tmp 2> /dev/null ; \
n> $(SHELL) $(srcdir)/move-if-change multilib.tmp multilib.out
n> it work fine for me!
Yes, this is a result of the change to backslash/newline handling in GNU
make 3.81. The new version obeys POSIX requirements and preserves the
backslash/newline pair in the script sent to the shell. See the NEWS file.
I'm not 100% sure why that's a syntax error, but...
n> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27023
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
