Hello, I would like to make a proposal for one aspect of the gcc 3.2 migration in sid. A critical part of this transition will be the discovery of how many arches still require creation of libgcc-compat code in glibc. Currently we are told by Jakub Jelinek that i386 is fine. Franz Sirl has just finished ppc in both branches of the glibc cvs. The ia64 arch has a version available in the glibc trunk that could be backported. Jakub also said alpha and sparc32 should be fine (not sure if that needs backported from the trunk though into glibc-2-2-branch). The rest will have to be handled by the arch maintainers here. After talking to Daniel Stone, I found out that the kde 3.0.3 introduction to sid was being delayed until the gcc 3.2 switchover has occurred. Since the scheme above will greatly delay kde 3.0.3 being added to sid, I would like to propose the following. Assuming each arch passes their gcc 3.2 testsuite and the most current binutils is mandated for use with gcc 3.2, we should be able to short-circuit the process as follows.
1) adjust the debian/control in glibc to build all arches at their current gcc < 3.1 regardless if gcc 3.2 is installed. 2) switch the gcc-default to gcc 3.2 3) as each arch can demonstrate that their libgcc-compat issues are resolved, their arch would be switched over in the glibc debian/control file to build glibc with gcc 3.2. This approach has the advantages of making the transition to gcc 3.2 go much faster while removing the need for each arch to immediately resolve their issues with libgcc-compat. All comments and suggestions are welcome. Jack