On Tue, Jan 30, 2018 at 11:18 AM, Cory Fields wrote:
> On Tue, Jan 30, 2018 at 2:14 PM, H.J. Lu wrote:
>> On Tue, Jan 30, 2018 at 11:07 AM, Cory Fields wrote:
>>> On Tue, Jan 30, 2018 at 1:35 PM, H.J. Lu wrote:
On Tue, Jan 30, 2018 at 10:26 AM, Cory Fields wrote:
> Hi list
>
>
On Tue, Jan 30, 2018 at 2:14 PM, H.J. Lu wrote:
> On Tue, Jan 30, 2018 at 11:07 AM, Cory Fields wrote:
>> On Tue, Jan 30, 2018 at 1:35 PM, H.J. Lu wrote:
>>> On Tue, Jan 30, 2018 at 10:26 AM, Cory Fields wrote:
Hi list
I'm playing with -static-pie and musl, which seems to be in g
On Tue, Jan 30, 2018 at 11:07 AM, Cory Fields wrote:
> On Tue, Jan 30, 2018 at 1:35 PM, H.J. Lu wrote:
>> On Tue, Jan 30, 2018 at 10:26 AM, Cory Fields wrote:
>>> Hi list
>>>
>>> I'm playing with -static-pie and musl, which seems to be in good shape
>>> for 8.0.0. Nice work :)
>>>
>>> However, t
On Tue, Jan 30, 2018 at 1:35 PM, H.J. Lu wrote:
> On Tue, Jan 30, 2018 at 10:26 AM, Cory Fields wrote:
>> Hi list
>>
>> I'm playing with -static-pie and musl, which seems to be in good shape
>> for 8.0.0. Nice work :)
>>
>> However, the fact that "gcc -static -pie" and "gcc -static-pie"
>> produc
On Tue, Jan 30, 2018 at 10:26 AM, Cory Fields wrote:
> Hi list
>
> I'm playing with -static-pie and musl, which seems to be in good shape
> for 8.0.0. Nice work :)
>
> However, the fact that "gcc -static -pie" and "gcc -static-pie"
> produce different results is very unexpected. I understand the c
Hi list
I'm playing with -static-pie and musl, which seems to be in good shape
for 8.0.0. Nice work :)
However, the fact that "gcc -static -pie" and "gcc -static-pie"
produce different results is very unexpected. I understand the case
for the new link-type, but merging the options when possible w
> On Jan 30, 2018, at 7:00 AM, Segher Boessenkool
> wrote:
>
> On Mon, Jan 29, 2018 at 05:00:00PM -0500, Paul Koning wrote:
>> It's been a few months since I tried to build GCC on my Mac, and in earlier
>> tries it worked fine. I have a log from 20-Sep-2017 that shows success.
>>
>> But cur
On Mon, Jan 29, 2018 at 05:00:00PM -0500, Paul Koning wrote:
> It's been a few months since I tried to build GCC on my Mac, and in earlier
> tries it worked fine. I have a log from 20-Sep-2017 that shows success.
>
> But currently when I do the same configs as before, I get failures about
> _ic
Well, as I said, I was mistaken and the .symver directive does actually
work for this, but the point of forcing the version is to provide a
backwards compatible binary. If I compile with GCC on a modern system, it
might generate a call to memcpy@GLIBC_2.14, so then that binary won't run
on a system
