[patch] Allow build to specify what sed mkheaders uses
Paolo Bonzini
bonzini@gnu.org
Fri Aug 28 13:56:00 GMT 2009
On 08/28/2009 01:32 AM, Steve Ellcey wrote:
> I did a bit more checking, it looks like if I run configure directly in
> the fixincludes directory with 'SED=/usr/bin/sed' as an argument on the
> configure line then I do use that SED command. Previously what I was
> doing was putting 'SED=/usr/bin/sed' on the top-level GCC configure
> command. It looks like that does not get passed down to the fixincludes
> configure script and so fixincludes then does not use /usr/bin/sed. If
> I do 'export SED=/usr/bin/sed' before calling the top-level configure
> script, then fixincludes will use /usr/bin/sed. So the issue may not be
> AC_PROG_SED but in how the top-level GCC configure calls
> sub-configure's. Maybe we need to add SED to the list of variables
> exported from the top-level GCC Makefile.
Yes, that would be a very small patch in Makefile.tpl, plus adding
AC_PROG_SED to the toplevel configure.ac.
Can you test this?
Paolo
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: configure-sed.patch
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20090828/591ed33c/attachment.ksh>
More information about the Gcc-patches
mailing list