On Wed, 6 May 2009 20:52:33 +0000 (UTC) "Joseph S. Myers" <joseph@xxxxxxxxxxxxxxxx> wrote: > The simplest thing is certainly just going with trunk (after 2.10 > branches) and ignoring compatibility with previous versions. But that > depends on whether users will be OK with a future ABI break. It is > possible to use GLIBC_2.11 versions on a past branch if you backport > Ulrich's version of my patch to allow GLIBC_2.10 versions to sort > correctly in version lists. I think using said patch is probably a sensible solution, where can I find this patch? Also in the current systems I've got, I've neglected to put a DEFAULT symbol version at all, meaning everything is using symbol versions right down to GLIBC_2.0 etc. Is there anyway to do a symbol version bump to GLIBC_2.11 without having to completely start from scratch? Obviously things are going to need to be recompiled anyway due to the elf machine number, but it would be nice to be able to rebuild everything using the currently built packages, rather than cross building everything from scratch again. Obviously this isn't a problem with the elf machine number due to ELF_MACHINE_ALT1 as you mentioned, but is this possible with a symbol version bump such as this? Regards, Bradley Smith -- Bradley Smith brad@xxxxxxxxxxxxxxxx Debian GNU/Linux Developer bradsmith@xxxxxxxxxx GPG: 0xC718D347 D201 7274 2FE1 A92A C45C EFAB 8F70 629A C718 D347
Attachment:
signature.asc
Description: PGP signature