On 26 Jan 2012, at 04:47, Eitan Adler wrote:
> On Wed, Jan 25, 2012 at 3:51 PM, Andriy Gapon wrote:
>> on 25/01/2012 15:23 David Chisnall said the following:
>>> On 22 Jan 2012, at 19:25, David Schultz wrote:
Technically it's a problem with python. If you ask for a strict
POSIX enviro
on 26/01/2012 06:47 Eitan Adler said the following:
> On Wed, Jan 25, 2012 at 3:51 PM, Andriy Gapon wrote:
>> on 25/01/2012 15:23 David Chisnall said the following:
>>> On 22 Jan 2012, at 19:25, David Schultz wrote:
Technically it's a problem with python. If you ask for a strict
POSIX e
On Thu, Jan 26, 2012, David Chisnall wrote:
>
> On 26 Jan 2012, at 04:47, Eitan Adler wrote:
> > What about patching python to only define the POSIX macros iff glibc
> > is being used (and getting this upstreamed) ?
That's a good strategy regardless. As long as python is doing
something bogus, i
On 26 Jan 2012, at 14:00, David Schultz wrote:
> On Thu, Jan 26, 2012, David Chisnall wrote:
>>
>> On 26 Jan 2012, at 04:47, Eitan Adler wrote:
>>> What about patching python to only define the POSIX macros iff glibc
>>> is being used (and getting this upstreamed) ?
>
> That's a good strategy r
On Thu, 26 Jan 2012, David Schultz wrote:
On Thu, Jan 26, 2012, David Chisnall wrote:
On 26 Jan 2012, at 04:47, Eitan Adler wrote:
What about patching python to only define the POSIX macros iff glibc
is being used (and getting this upstreamed) ?
That's a good strategy regardless. As long a
