[Bug java/28024] libjava build failure on Solaris 2.8 (sun4u)

["bob at digilink dot net" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #8 from bob at digilink dot net  2006-06-16 09:13 -------
(In reply to comment #6)
> > I fixed this problem.  But, as I don't have a Solaris box,
> > I can't test whether this means that the build works.
> 
> This report was actually invalid, we don't support /bin/sh on Solaris.
> 

I would like to thank Tom for the amazingly fast response to this bug - and to
also apologize for the fact that I have been unable to actually test his fix
yet.

Given that the problem is solvable, it seems more than just a little odd that
your reply is "We don't support /bin/sh on Solaris"

My simple question is why not support /bin/sh on Solaris?

Having to specify the shell for the config script is more than a little obtuse
given that I haven't encountered a single open source software package that
requires this and I have been dealing with open source software for the last
13+ years on Solaris. I thought that I had read all of the Solaris notes for
building 4.1.1 but even with that effort I missed the link you pointed me to.
gcc 4.1.1 for c and c++ compile just fine with /bin/sh for Solaris. If java is
going to be 'different' then it should not be included as a standard build
language. I don't need it and I'm fairly certain the majority of people
building gcc don't need it.

If the compatibility with /bin/sh can be solved, why not. The result will be
less hassle with bugs like this being filed.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28024