sed: command garbled

[Phil Edwards <pedwards at disaster dot jaj dot com>]

This change

    2000-07-27  Alexandre Oliva  <aoliva@redhat.com>

            * Makefile.in (clean-target-libgcc): Remove gcc/libgcc.
            (clean-target): Depend on it.

            * Makefile.in (FLAGS_FOR_TARGET): New macro.
            (GCC_FOR_TARGET): Use it.
            (CC_FOR_TARGET, CXX_FOR_TARGET, CHILL_FOR_TARGET): Now defined...
            * configure.in: ... here.
            (FLAGS_FOR_TARGET): Define.  Add ld build dir to -L path.
            (libstdcxx_flags): Define and append to CXX_FOR_TARGET.

breaks a build when libstdc++-v3 is enabled:

    % gmake all
    sed: command garbled: s/-I/-isystem
    /bin/sh: -L/stuff/pme/3test/sparc-sun-solaris2.8/libstd++-v3/src: not found
    gmake[1]: Entering directory `/stuff/pme/3test/libiberty'
    gmake[1]: *** No rule to make target `/g'.  Stop.
    gmake[1]: Leaving directory `/stuff/pme/3test/libiberty'
    gmake: *** [all-libiberty] Error 2
    % 

because the sed script (s/-I/-isystem /g) passed with -e inside
libstdcxx_flags is enclosed with double quotes instead of single quotes.

I can edit the $builddir's generated Makefile and replace them with
single quotes, and then it's okay.  I /think/ that replacing a " with a
\' in the $srcdir's configure.in would be okay, but I don't know how the
top-level config stuff gets generated, or not, or not-quite-automatically
generated, etc.  So, no patch.  Sorry.

(What is "Cygnus configure" and why is it used in the top-level instead
of autoconf?  Or would I be happier not knowing?  :-)


Phil