This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: sed: command garbled
- To: aoliva at redhat dot com
- Subject: Re: sed: command garbled
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Thu, 3 Aug 2000 19:17:06 -0400
- Cc: gcc-bugs at gcc dot gnu dot org
Combining your messages...
> What do you get for CXX_FOR_TARGET in the top-level Makefile?
This is going to be horribly linewrapped...
CXX_FOR_TARGET = $$r/gcc/g++ -nostdinc++ `test "x$$dir" != xlibstdc++-v3 &&
test -f $$r/$(TARGET_SUBDIR)/libstdc++-v3/mkcheck &&
$(SHELL) $$r/$(TARGET_SUBDIR)/libstdc++-v3/mkcheck 2
$$r/$(TARGET_SUBDIR)/libstdc++-v3 $$s/libstdc++-v3 | sed -e "s/-I/-isystem /g"`
-L$$r/$(TARGET_SUBDIR)/libstd++-v3/src
-L$$r/$(TARGET_SUBDIR)/libstd++-v3/src/.libs $(FLAGS_FOR_TARGET)
> > P.S.- Should that top-level configure.in really have /bin/bash as its
> > #! invocation line? I'm all for a Bourne shell that doesn't suck,
> > but is that safe?
>
> It just doesn't matter at all. configure.in is always run with
> ${CONFIG_SHELL-/bin/sh}.
Ah. Maybe it should be #!/bin/ignored or something.
> Let me guess: are you running Solaris? Solaris' /bin/sh behaves
> differently regarding nested backticks and quotes. That must be the
> problem. Oh, well, back to the drawing board... :-(
Uck. Solaris' /bin/sh is non-POSIX-compliant, and due to demands from very
well-paying customers, it's apparently not going to change. (According to
Sun employees on Usenet.)
If CONFIG_SHELL is set to bash v2, it works. With sh and ksh (the POSIX
sh on Solaris), it fails.
Phil