Darren J Moffat wrote:
> Your justification supports using binutils 2.17 over 2.18 because of a
> 2.18 but but it doesn't follow that you create this gcc4 subdir, because
> your rationale has nothing to do with gcc4 but to do with a bug in
> binutils 2.18. If the idea is to support multiple copies of binutils
> then IMO the dir structure should be more like
> /usr/gnu/binutils/2.17/bin/. However I still don't see the point in
> that, since 2.18 isn't incompatible it is just plain broken on Solaris.
Actually, no.
The idea behind this directory structure (which appears to get drowned in
static) is the following:
/usr/gnu/gcc4/{bin,lib,include,man,share} will deliver the binutils for GCC4 --
whatever version these are. Right now, it's version 2.17. This could be
upgraded
in the future.
/usr/gnu/gcc4/<Major>.<Minor>.<Micro>/{bin,lib,libexec,include,share,etc} can
deliver several (more than one) versions of GCC4: 4.3.2, 4.4.3, etc, like so:
/usr/gnu/gcc4/4.3.2/{bin,lib,libexec,include,share,etc}
/usr/gnu/gcc4/4.4.3/{bin,lib,libexec,include,share,etc}
etc etc etc
This way we can deliver several different versions of GCC4, depending on needs,
or requests, and have all of them use the same binutils.
--Stefan
--
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM
