Darren J Moffat wrote: > Stefan Teleman wrote: >> >> >> Darren J Moffat wrote: >> >>> This is on the assumption that GNU binutils 4.3.x is NOT incompatible >>> with the gcc we currently ship. If GNU binutils *is* incompatible >>> with the gcc we currently ship then IMO this case needs to wait and >>> be part of a future case that upgrade gcc as well, otherwise I don't >>> see the point in shipping the newer binutils if we ship the older >>> compiler (unless the newer binutils are compatible with the compiler >>> we ship). >> >> For the record: I am *purposely* introducing binutils _first_. > > Then this case is incomplete as I can't see the bigger picture with how > this fits with GCC4, hence the questions about the gcc4 directory. > Please either roll them into one case or provide an overview.
This case is not incomplete. I have already explained why binutils is independent of GCC, why it must be introduced independently of GCC, and why binutils must already be installed on the system before configuring and installing GCC. Independently of this, binutils has a completely different release schedule and versioning scheme than GCC. Combining this (binutils) ARC Case with future GCC ARC Cases would be akin to combining GNU MP Bignum with MPFR in the same ARC Case, simply because MPFR depends on GNU MP bits, or combining Python and LCMS in the same ARC Case, for the same reasons. This is the binutils ARC Case. Any future GCC4 ARC Cases are purposely designed to be independent from it. We must be able to update binutils in the future, without having to touch existing GCC4 ARC Cases, and vice-versa. My expectation is that GCC will ARC more often than binutils. Compatibility constraints between any future version of binutils, and any existing installed GCC4 bits must be ascertained prior to filing such future binutils ARC Cases. If a future version of binutils is incompatible with any existing GCC4's, thereby breaking them, then that future version of binutils simply cannot be used. The GCC4 ARC Case [ GCC 4.3.2 ] will be filed shortly. The new GCC 4.3.2 ARC Case will reference the binutils 2.17 ARC Case (_this_ one). Future GCC4 ARC Cases will reference this same binutils ARC Case. Not the other way around. GCC depends on binutils, binutils couldn't care less which versions of GCC use its bits, or how many GCC versions are already installed, or where they are installed. The architectural Big Picture as to why a certain directory structure has been chosen will become obvious once the first GCC4 ARC Case is submitted. It is already known that different GCC versions cannot coexist within the same directory structure, and must be delivered under separate directory paths. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman at Sun.COM
