On Wed, 27 Jan 2016, Balint Reczey wrote: > +--- a/config.guess > ++++ b/config.guess > +@@ -145,6 +145,8 @@ Linux|GNU|GNU/*) > + LIBC=uclibc > + #elif defined(__dietlibc__) > + LIBC=dietlibc > ++ #elif defined(__GNU_FEATURESET_HARDENED1__) > ++ LIBC=gnuhardened1 > + #else > + LIBC=gnu > + #endif
I see in #812782 that the new name is not stable yet (let alone accepted by upstream)... this is certainly too early to ask for any changes in autotools-dev. Also, as far as I know, a new arch triplet is not supposed to suddenly become incompatible with itself, so you'd need to set in stone what that new libc ABI will mean. But I might be wrong about this, talk to glibc and GNU config upstreams to confirm it. Anyway, GNU config changes *really* needs to be done upstream first. It completely destroys forward-compatibility in GNU config, otherwise. Destroying forward-compatibility creates trouble for software developers (Debian users) that do upstream software development work using Debian. So, please talk to upstream (GNU config, glibc) about what you want to do, and what you need. After the changes you need get merged upstream, contact me and I will be happy to fast-track an autotools-dev upload with the new upstream version, as I always did for every new arch and port that needed it. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
