This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Document that --enable-static-pie implies PIE
- From: Jonathan Nieder <jrnieder at gmail dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 19 Dec 2017 12:46:41 -0800
- Subject: Re: [PATCH] Document that --enable-static-pie implies PIE
- Authentication-results: sourceware.org; auth=none
- References: <20171219185156.GA25849@gmail.com> <20171219193522.GA240141@aiede.mtv.corp.google.com> <CAMe9rOqj=uBgJ=nvXU4ndWkYm3Ergbhok_ZaD3UYEodQ5XSFzQ@mail.gmail.com>
H.J. Lu wrote:
> On Tue, Dec 19, 2017 at 11:35 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> When the new text says that dynamic PIE is created by default, what does
>> that mean? Does it mean that my executables will automatically act as
>> though I passed -fPIE by default when I link them or that support for
>> -fPIE will be included in glibc? If the latter, is it saying that such
>> support will be included in the glibc distribution by default but that I
>> can turn it off? i.e. what is the option to unset this default, or what
>> would be the option to turn it on if I don't --enable-static-pie?
>
> How about
>
> This option also implies that glibc programs and tests are created as
> dynamic position independent executable (PIE) by default.
With s/executable/executables/, LGTM.
>> Unrelated: while I'm reading this text
>>
>>> Static PIE is similar to static executable,
>>
>> This is missing an article.
[...]
> Can you submit a separate patch?
Sure thing. Will try to find time to send one tonight.
Thanks,
Jonathan