Fallout (mostly runtime library-related) from GCC version number change

[Joseph S. Myers]

On Wed, 16 Mar 2005, Zack Weinberg wrote:

> The primary observed bug in the previous patch was that $(libsubdir)
> isn't set correctly; things get installed into
> $(prefix)/lib/gcc/$(target_alias)/const (yes, "const"; I don't know
> where that's coming from) instead of the proper .../$(gcc_version).

Also libexecsubdir, parts of which get "4.1.0" and parts of which get 
"const".  Does fixincludes/mkheaders.in's definition of libexecsubdir 
still work after this patch?

gcc/Makefile.in's

        "libexecsubdir=$(libsubdir)" \

seems dodgy, but this is pre-existing and may be harmless.

libmudflap seems unaddressed by this patch and looks like it uses the old 
version numbering scheme.

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)