This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH, libgfortran] Remove AM_MAKEFLAGS.
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Steve Ellcey <sje at cup dot hp dot com>
- Cc: paul at codesourcery dot com, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Wed, 08 Dec 2004 17:37:51 -0500
- Subject: Re: [PATCH, libgfortran] Remove AM_MAKEFLAGS.
- References: <200412082221.OAA29266@hpsje.cup.hp.com>
I have not built a cross-compiler with libgfortran.
BTW, because the Makefile rule to build environ.lo is
$(LIBTOOL) --mode=compile $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -c -o environ.lo `test -f 'runtime/environ.c' || echo '$(srcdir)/'`runtime/environ.c
the only way that "(CC_FOR_TARGET)" would appear in place of $(CC) is if
it *were* getting substituted for CC but substituted incorrectly. It is
substituting it literally instead of expanding it.
I would add some commands to the libgfortran Makefile manually to
see what values of $(CC) and $(CC_FOR_TARGET) it is receiving.
Are you using GNU Bash or HP-UX Shell? It might be a shell
problem or the version of Make. I do not have any intuition about the
difference between native and cross build in this case. Could the cross
build accidentally be invoking a different shell?
I'm fairly confident that the AM_MAKEFLAGS change was fixing the
symptom and not the problem.