glibc 2.24 -- Release blockers

[Paul Eggert]

On 07/14/2016 12:46 PM, Sinny Kumari wrote:
>> I guess it explains also emacs build failure in rawhide -
>> >http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=3535700
> Indeed, it affected emacs build on ppc64(le) . emacs build failure on
> ppc64(le) was giving message
> "Memory exhausted--use M-x save-some-buffers then exit and restart Emacs".

The Emacs build procedure is supposed to work around this sort of 
problem by running a command like this:

setfattr -n user.pax.flags -v er temacs

immediately after building temacs. Is there some way to tell whether the 
setfattr command was not installed correctly on that rawhide build? 
Unfortunately the URL above doesn't seem to let me look at the build log.