On May 14 09:17, Christopher Faylor wrote:
> On Mon, May 14, 2007 at 07:13:28AM -0600, Eric Blake wrote:
> >According to Christopher Faylor on 5/14/2007 6:53 AM:
> >>>Does cygwin care about providing reentrant versions of functions?
> >>>There is precedent for doing this: as an example, cygwin.din
On Mon, May 14, 2007 at 07:13:28AM -0600, Eric Blake wrote:
>According to Christopher Faylor on 5/14/2007 6:53 AM:
>>>Does cygwin care about providing reentrant versions of functions?
>>>There is precedent for doing this: as an example, cygwin.din already
>>>exports asprintf_r.
>>
>>That was probab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 5/14/2007 6:53 AM:
>> Does cygwin care about providing reentrant versions of functions?
>> There is precedent for doing this: as an example, cygwin.din already
>> exports asprintf_r.
>
> That was probably one of many
On Mon, May 14, 2007 at 06:47:27AM -0600, Eric Blake wrote:
>According to Christopher Faylor on 5/14/2007 6:25 AM:
>>Why do we need to export *vdprintf_r at all? Does some standard define
>>it?
>
>Does cygwin care about providing reentrant versions of functions?
>There is precedent for doing this:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 5/14/2007 6:25 AM:
> Why do we need to export *vdprintf_r at all? Does some standard define it?
Does cygwin care about providing reentrant versions of functions? There
is precedent for doing this: as an example, cy
On Mon, May 14, 2007 at 06:22:54AM -0600, Eric Blake wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>According to Corinna Vinschen on 5/14/2007 6:12 AM:
>>> _Exit
>>> dprintf
>>>
>>> There is also a big list of integer-only and reentrant variants of *printf
>>> that
>>> might be worth e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 5/14/2007 6:12 AM:
>> _Exit
>> dprintf
>>
>> There is also a big list of integer-only and reentrant variants of *printf
>> that
>> might be worth exporting:
>>
>> asiprintf, _asiprintf, asiprintf_r, _asiprintf_r, dipr
On May 1 22:55, Eric Blake wrote:
> I noticed a couple of functions that cause link errors even though they are
> required by POSIX (or at least will be required by the next version of
> POSIX),
> implemented by newlib, and declared in the headers:
>
> _Exit
> dprintf
>
> There is also a big
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Samuel Thibault on 5/1/2007 5:02 PM:
> Eric Blake, le Tue 01 May 2007 22:55:11 +, a écrit :
>> I noticed a couple of functions that cause link errors even though they are
>> required by POSIX (or at least will be required by the next
Eric Blake, le Tue 01 May 2007 22:55:11 +, a écrit :
> I noticed a couple of functions that cause link errors even though they are
> required by POSIX (or at least will be required by the next version of
> POSIX),
> implemented by newlib, and declared in the headers:
>
> _Exit
> dprintf
Mm
I noticed a couple of functions that cause link errors even though they are
required by POSIX (or at least will be required by the next version of POSIX),
implemented by newlib, and declared in the headers:
_Exit
dprintf
There is also a big list of integer-only and reentrant variants of *printf
11 matches
Mail list logo
