-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding bug-gnulib; and please consider using more descriptive subject lines]
According to Elbert Pol on 10/12/2008 3:33 AM:
> Hello,
>
> Tried today m4.1.4.12
> With os/2 and gcc 4.32
>
>
> And it failed @ the make
>
> Included the logs...
[no n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding bug-gnulib]
According to Nelson H. F. Beebe on 10/14/2008 2:23 PM:
> Builds of m4-1.4.12 fail on Apple Mac OS X 10.x PowerPC systems
> with this error:
>
> gcc -std=gnu99 -I. -I../lib -I. -I. -I.. -I./.. -I../lib -I./../lib
> -I/usr/
Simon Josefsson wrote:
> Maybe something for the 'sockets' module, it is rather Windows specific?
Hmm, I see the 'sockets' module more like the general facilities, that
everyone who uses sockets needs. I would therefore somewhat prefer to see
the declaration of this function in and its implementa
In message <[EMAIL PROTECTED]>, Eric Blake writes:
>Quotes won't help; the shell then tries to evaluate the command 'unset FOO'
>with no arguments, because there is no reason to do IFS splitting.
Doh.
>But this works, using an intermediate variable, so that IFS splitting still
>occurs:
>$ /bin
Peter Seebach seebs.net> writes:
> >> ${FOO+unset FOO}
> >>
> >No, it does NOT work in Solaris sh (tested on Solaris 8):
> >
> I think it needs to be in quotes, as with other {x+a b} expansions.
Quotes won't help; the shell then tries to evaluate the command 'unset FOO'
with no arguments, beca
Jim Meyering <[EMAIL PROTECTED]> wrote:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> Jim Meyering <[EMAIL PROTECTED]> writes:
>>
>>> Does anyone object to my installing a server-side hook
>>> that would prevent pushing merge commits on master?
>>> In our experience here (with gnulib.git), pushin
In message <[EMAIL PROTECTED]>, Eric Blake writes:
>Peter Seebach seebs.net> writes:
>
>>
>> In regards to worries about "unset FOO" not working if FOO is not set:
>>
>> ${FOO+unset FOO}
>>
>> Is this crazy or clever? It works in Solaris sh. (I know, in most cases,
>> it's sufficient to just
Peter Seebach seebs.net> writes:
>
> In regards to worries about "unset FOO" not working if FOO is not set:
>
> ${FOO+unset FOO}
>
> Is this crazy or clever? It works in Solaris sh. (I know, in most cases,
> it's sufficient to just empty the variable, but sometimes it'd be nice to
> be able
> If there is a way to reliably check whether something is a HANDLE or not
> (or a low-level fd or not), the code could be re-written to cleanly
> treat them as separate objects, and thus be more reliable.
Both HANDLEs and fds are indexes into a table, in the end. So you can
check if X is a HAND
> Maybe something for the 'sockets' module, it is rather Windows specific?
> How about the patch below?
You maintain the module; but yes, it's fine by me.
Paolo
Paolo Bonzini <[EMAIL PROTECTED]> writes:
>> I need to pass a SOCKET handle to GnuTLS, instead of the FD handle that
>> winsock wrappers created.
>
> You can also install your own GnuTLS transport handlers using read and
> write. It would probably be less code and less complication than
> togglin
Bruno Haible <[EMAIL PROTECTED]> writes:
> Hi Simon,
>
>> As we discussed earlier, and as far as I understand, the only approach
>> for a project like libgnutls -- that needs compatibility with native
>> Windows programs -- is to accept a SOCKET handle from the application,
>> and call the native
> I need to pass a SOCKET handle to GnuTLS, instead of the FD handle that
> winsock wrappers created.
You can also install your own GnuTLS transport handlers using read and
write. It would probably be less code and less complication than
toggling between descriptors and sockets.
>> SOCKET _gl_fd
13 matches
Mail list logo
