On Fri, 13 Jun 2014 09:38:32 -0400
Rich Freeman wrote:
> On Fri, Jun 13, 2014 at 9:22 AM, Jeroen Roovers wrote:
> > The problem I see is that anyone who wants to switch to having
> > -fstack-protector enabled by default early will run into the glibc
> > problem (much as I did), when all the bug
Hello, all.
Attaching two patches: one that practically rewrites
python_fix_shebang, and the other one that adds proper tests for it.
Major changes:
1. I replaced unclear space magic that attempted to handle corner cases
with plain 'for i in ${shebang}' -- trying to match various python*
pattern
On 06/13/2014 14:08, Greg Turner wrote:
> On Fri, Jun 13, 2014 at 6:38 AM, Rich Freeman wrote:
>> add the strip-flags statement to the ebuild and be done
>> with it
>
> To do it "greenly" we'd obviously want to know the precise surface
> area of the problem and then to correctly express those cir
On 06/13/2014 14:41, Joshua Kinard wrote:
> On 06/13/2014 14:08, Greg Turner wrote:
>> On Fri, Jun 13, 2014 at 6:38 AM, Rich Freeman wrote:
>>> add the strip-flags statement to the ebuild and be done
>>> with it
>>
>> To do it "greenly" we'd obviously want to know the precise surface
>> area of th
On 06/13/2014 14:08, Greg Turner wrote:
> On Fri, Jun 13, 2014 at 6:38 AM, Rich Freeman wrote:
>> add the strip-flags statement to the ebuild and be done
>> with it
>
> To do it "greenly" we'd obviously want to know the precise surface
> area of the problem and then to correctly express those cir
On Fri, Jun 13, 2014 at 6:38 AM, Rich Freeman wrote:
> add the strip-flags statement to the ebuild and be done
> with it
To do it "greenly" we'd obviously want to know the precise surface
area of the problem and then to correctly express those circumstances
in eblit code that could stand up to th
On Fri, Jun 13, 2014 at 9:22 AM, Jeroen Roovers wrote:
> The problem I see is that anyone who wants to switch to having
> -fstack-protector enabled by default early will run into the glibc
> problem (much as I did), when all the bug reports that point out the
> problem have been closed as INVALID.
On Thu, 12 Jun 2014 23:43:55 -0600
Ryan Hill wrote:
> On Wed, 11 Jun 2014 15:23:15 +0200
> Jeroen Roovers wrote:
>
> > Will bug #332823 and its ilk somehow be mitigated? Emerging glibc
> > with -fstack-protector still leads to similar problems. There
> > doesn't currently seem to be a bug repor
