--- Comment #8 from marc dot glisse at normalesup dot org 2008-11-12 16:30
---
The comments already say this bug is a duplicate (of a now fixed bug), I am
just marking it for cleanup. Hope that is the right thing to do...
*** This bug has been marked as a duplicate of 27843 ***
--
--- Comment #7 from jamesc at dspsrv dot com 2007-02-20 13:08 ---
This happened me on solaris 10 (even with reading the manual!) make install had
worked for me previously on solais without having to set CONFIG_SHELL so it is
something that might trip people up.
I agree that this is a dup
--- Comment #6 from Ralf dot Wildenhues at gmx dot de 2007-02-16 17:40
---
This is a duplicate of 27843 (Solaris and Tru64 /bin/sh share the same issue),
which has been resolved as fixed. :-)
Someone empowered enough please reflect this in the settings, thank you!
--
http://gcc.g
--- Comment #5 from marc dot glisse at normalesup dot org 2006-12-08 12:19
---
(In reply to comment #4)
> Except you did not read instructions so what is the difference?
Ok say you forget I mentionned solaris /bin/sh. I just believe it would be more
consistant to use single quotes inst
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-08 05:00 ---
(In reply to comment #3)
> Sure, it works with a posix shell.
Except you did not read instructions so what is the difference?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30083
--- Comment #3 from marc dot glisse at normalesup dot org 2006-12-07 11:04
---
Sure, it works with a posix shell. But it would not hurt to use single quotes
around the constant string passed as an argument to sed, as is done in the rest
of the file, if only for consistancy. It seems to
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-12-06 23:05 ---
Solaris's /bin/sh is not a POSIX shell, please read http://gcc.gnu.org/install/
and try again.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30083
--- Comment #1 from marc dot glisse at normalesup dot org 2006-12-06 18:01
---
Actually, the problem seems to be caused by the '^' character, which is the
equivalent of '|' for this shell. The solution is still the same, have single
quotes (or protect the '^' with '\'). There seems to b
