Hi Mark, On 24-07-2017 16:17, Mark Wielaard wrote: >>> We normally keep elf.h in sync with glibc. >>> Could you submit this elf.h change to libc-al...@sourceware.org? >>> Then we resync elf.h from glibc to pull in the new constants. >> >> It looks like glibc community won't review / push that change as it is in >> freeze for glibc 2.26 cut right now accordingly to [1]. >> >> If my understanding is correct, it's a blocker or my change can be pushed >> to elfutils and once glibc is open again (in about a week) I can submit >> this elf.h change to libc-al...@sourceware.org? > > Lets call it a soft-block :) It is just that I hate the files getting > out of sync. We risk using slightly differently named constants. It > looks like the 2.26 release will be next week, so hopefully the freeze > will be over end of this week. > > Could you post the fix to libc-alpha already and then ping it next > week once the tree open up again? Then I'll push your patch to > elfutils.
Posted: https://sourceware.org/ml/libc-alpha/2017-07/msg00827.html Thank you and best regards, Gustavo
