Re: [PATCH] strdup: undeprecate, IRIX 6.5 needs it

Eric Blake writes: > * modules/strdup (Status): No longer obsolete. > * doc/posix-functions/strdup.texi (strdup): Document this. Thanks, although it may be premature given Bruno's comment. I'll try to debug it further. /Simon

Re: Is IRIX 6.5 obsolete?

Bruno Haible writes: > Hi Simon, > >> Do we want to support IRIX 6.5? It doesn't appear to have strdup: >> >> cc-1515 c89: ERROR File = client.c, Line = 45 >> A value of type "int" cannot be assigned to an entity of type "char *". >> *output = strdup (p); >> ^ >> 1 error detec

Re: Is IRIX 6.5 obsolete?

Hi Simon, > Do we want to support IRIX 6.5? It doesn't appear to have strdup: > > cc-1515 c89: ERROR File = client.c, Line = 45 > A value of type "int" cannot be assigned to an entity of type "char *". > *output = strdup (p); > ^ > 1 error detected in the compilation of "client

[PATCH] strdup: undeprecate, IRIX 6.5 needs it

Reported by Simon Josefsson. * modules/strdup (Status): No longer obsolete. * doc/posix-functions/strdup.texi (strdup): Document this. Signed-off-by: Eric Blake --- >> Would this be a reason to un-deprecate the 'strdup' module? >That's easy, right? and would solve the problem? >So let's go with

Re: Is IRIX 6.5 obsolete?

On 05/21/2012 01:42 PM, Simon Josefsson wrote: > Would this be a reason to un-deprecate the 'strdup' module? That's easy, right? and would solve the problem? So let's go with that.

Is IRIX 6.5 obsolete?

Do we want to support IRIX 6.5? It doesn't appear to have strdup: cc-1515 c89: ERROR File = client.c, Line = 45 A value of type "int" cannot be assigned to an entity of type "char *". *output = strdup (p); ^ 1 error detected in the compilation of "client.c". Would this be a rea

select.c:496: error: `NULL' undeclared

I got this error on a IRIX 6.5 system: checking for sys/select.h... yes checking whether is self-contained... no checking whether pselect is declared without a macro... no checking whether select is declared without a macro... no checking whether select supports a 0 argument... no ... CC se

Re: redoing gnulib import to avoid 8+3 glitches

Re , Eli Zaretskii wrote: > Could the offending file be renamed in gnulib in some way that > eliminates the problem? We asked about that earlier, and the consensus on the gnulib side was that porting to 8+3 file name restrictions was outside gnulib's scope. The solutio

[PATCH] gc: fix libgcrypt detection on older machines.

I've pushed this. /Simon * m4/gc.m4: Reject libgcrypt earlier than 1.4.4. Collapse copyright years because the file has been distributed every year since it was created. --- ChangeLog |6 ++ m4/gc.m4 | 14 +++--- 2 files changed, 17 insertions(+), 3 deletions(-) diff --git a

[PATCH] fix errno for MinGW64

I noticed that errno doesn't work on Fedora 17's MinGW64 because it defines some of MSVC10's new error codes, but not all. This patch fixes it, while avoiding that glibc gets the replacement only because it lacks EOTHER (which is not even in POSIX). Ok? 2012-05-21 Paolo Bonzini errno

Re: [PATCH] poll: prevent busy-waiting

Here is what I applied. Thanks! 2012-05-21 Paolo Bonzini poll/select: prevent busy-waiting. SwitchToThread() only gives away the rest of the current time slice to another thread in the current process. So if the thread that feeds the file decscriptor we're pol

Re: [PATCH] gitlog-to-changelog: support the log message format used in Bison

Hi Jim, What do you think about the attached proposal? It started here: http://lists.gnu.org/archive/html/bug-gnulib/2012-05/msg00217.html Le 15 mai 2012 à 10:02, Akim Demaille a écrit : > > Le 14 mai 2012 à 17:19, Akim Demaille a écrit : > >> <0001-gitlog-to-changelog-support-the-log-message