🚀 go-pugleaf

In article <ABRAHAM.92Dec16110802@loke.iesd.auc.dk> abraham@iesd.auc.dk (Per Abrahamsen) writes:
>[changing versions] seldom gives problems with the other utilities, as the
>data format of the files they manipulate stay reasonable constant.  Not
>so with g++. 

But different versions of other utilities may have different bugs.

>The assembler, the linker, and the C libraries goes into 
>
>	$GNUHOME/lib/gcc-lib/$ARCH/$VERS

Only if you install them by hand.

>The only problem today is that libg++ for some reason is not assumed
>to be in that directory, both the gcc and the libg++ distribution
>seems to expect that all versions of gcc will share the same version
>of libg++.  This is a pain, and we have to change both by hand to
>correct the situation.

Do you have a suggestion?

>Bothner> The more general (and standard) way to select versions is by
>Bothner> installing different versions into different directories.

>And break object (and possibly source) code compatibility for all
>users when we install a new version of g++?

So use /gnu-921201/bin instead of /new/bin.  I don't see any
real difference between:
	/gnu-921201/bin/gcc -c foo.c
and:
	gcc -V921201 -c foo.c

My opinion is that gcc -V is a special-purpose, ad hoc way to
manage multiple versions.  I don't think it gives you anything you
can't do with appropriate converntions - and these conventions
are much easier to tailor to individual requirements (from
no versioning to very sophisticated schemes).

	--Per Bothner
Cygnus Support   bothner@cygnus.com  bothner@neon.stanford.edu