Steve Langasek writes: > On Wed, Apr 05, 2006 at 11:06:21PM +0200, Aurelien Jarno wrote: > > > A few weeks ago, the 2.4 kernels have been declared "deprecated" [1]. I > > would like to know what does this exactly mean: > > - That users are advised not to use them? > > - That we could drop support for them in other packages? > > - That they will be removed from the archive soon? > > It means 1), and should mean 3) as well. In general, it does *not* imply 2) > -- we need to be assured of having a clean upgrade path from sarge to etch, > and since sarge shipped with a 2.4 kernel by default, this means that etch > packages should at least be functional enough on 2.4 to allow a full upgrade > and subsequent reboot to a new kernel. (That includes not breaking the > system if the upgrade is interrupted and the system is rebooted again to a > 2.4 kernel before the upgrade completes.)
In light of #361024, what are our options? - configure gcc with --disable-tls (on which architectures would that be (not) needed?) - build a libstdc++6 with a gcc, configured with --disable-tls and ship two versions? Would that help the upgrade issue? Sheplyakov Alexei writes: > Current glibc does not support TLS under 2.4 kernels (see #226716), so > this is probalby glibc bug (some people call it feature). - provide TLS support for 2.4 kernels and an upgrade path? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
