[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5354FE0C.8020303@midipix.org>
Date: Mon, 21 Apr 2014 07:16:28 -0400
From: "writeonce@...ipix.org" <writeonce@...ipix.org>
To: musl@...ts.openwall.com
Subject: Re: static musl-based gdb and -fPIC
On 04/21/2014 04:21 AM, Szabolcs Nagy wrote:
> * Szabolcs Nagy <nsz@...t70.net> [2014-04-21 09:33:47 +0200]:
>> yes they define posix_ prefixed symbols for internal use
>> which are reserved names for the c implementation when
>> any standard headers are included
>>
>> the next posix standard defines posix_close so this is a
>> real collision (and will be an issue with every conformant
>> libc), but all the other posix_ symbols are wrong there too
> it seems it was already reported and "fixed"
> http://bugs.python.org/issue20594
>
> the fix is broken though
>
>
If I understand correctly, that "fix" is only in the 3.3/3.4 version.
For llvm/clang/lldb (latest release: 3.4), though, python 2.7 is the
highest supported version.
zg
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
