This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Replece LDFLAGS-* = $(no-pie-ldflag) with tst-*-no-pie = yes [BZ #22630]


On Tue, 19 Dec 2017, H.J. Lu wrote:

> On Tue, Dec 19, 2017 at 10:18 AM, Joseph Myers <joseph@codesourcery.com> wrote:
> > On Tue, 19 Dec 2017, H.J. Lu wrote:
> >
> >> >> To build static PIE, all .o files need to compiled with -fPIE.  Given all
> >> >> input .o files are compiled with -fPIE when creating an executable, should
> >> >> we generate PIE or nor no-PIE?
> >> >
> >> > I'd expect a normal executable, in the case of dynamic executables, since
> >> > nothing about --enable-static-pie says it changes how non-static
> >> > executables are built.
> >>
> >> I can certainly make a patch to do that.  On the other hand, should
> >> --enable-static-pie imply PIE?
> >
> > Logically, it doesn't need to.  Practically, I don't know if people will
> > want static PIEs without dynamic PIEs, but if it implies both static and
> > dynamic PIEs, the documentation needs to say so.
> >
> 
> I will submit a patch to update documentation.

If the documentation achieves consensus, then this patch is also OK, since 
I think it's the correct way in that context of avoiding trying to link 
these particular tests as PIE.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]