Re: PING^N: [PATCH] Add --enable-static-pie to build static PIE [BZ #19574]

[Joseph Myers <joseph@codesourcery.com>]

On Sat, 16 Dec 2017, H.J. Lu wrote:

> Thanks for your time.  I checked it in with the updated commit log.
> I also updated
> 
> https://sourceware.org/glibc/wiki/PortStatus

That's missing key information:

* It needs a complete list of architectures that have not yet been 
verified to work with static PIE.  Architectures would then be removed 
from that list one at a time as and when someone verifies them to work and 
commits any fixes needed (and if the list becomes empty, the whole 
section of the wiki page could be removed at that point).

* It needs instructions on how to test whether static PIE works for an 
architecture (or architecture/ABI pair, if appropriate).  Is this 
"configure --enable-static-pie and make sure test results are as good as 
without that option", or "configure --enable-static-pie and make sure 
tests X, Y and Z pass", or doing one of those but additionally using GCC 8 
or later so -static-pie is supported, or something else?  This needs to be 
on the wiki page so it's completely clear how someone can test the feature 
for an architecture and have confidence in whether it's working.

When new ports are submitted for glibc, you should then seek confirmation 
of whether they work with static-PIE, as if they don't and get added to 
glibc without such support, they'd need to be added to the list on the 
wiki page.

> for static PIE status.  Should build-many-glibcs.py be updated to also 
> build static PIE for i386, x86_64 and x32?  We can't build it by default 
> since the recent linker is needed.

A few additional builds for configurations where all the GCC / binutils / 
glibc support required is present would be a good idea (but maybe not if 
enough support isn't present in the default versions used by 
build-many-glibcs.py, which means GCC 7 branch and binutils 2.29 branch).

-- 
Joseph S. Myers
joseph@codesourcery.com