Hello,
Libunistring 0.9.1 fails to build on Solaris with Sun cc and Sun make:
--8<---cut here---start->8---
rm -f unistring/stdbool.h-t unistring/stdbool.h
{ echo '/* DO NOT EDIT! GENERATED AUTOMATICALLY! */'; \
echo '#if !defined _GL_STDBOOL_H'; \
if test
On Thu, Nov 26, 2009 at 08:29:38PM +0100, Paolo Bonzini wrote:
>> No I don't - can you apply it for me?
>
> Done.
Excellent, thanks.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
New in Fedora 11: Fedora Windows cross-compiler. Compile Windows
programs,
No I don't - can you apply it for me?
Done.
Paolo
On Thu, Nov 26, 2009 at 08:22:47PM +0100, Paolo Bonzini wrote:
> On 11/26/2009 05:52 PM, Richard W.M. Jones wrote:
>>
>> Currently any socket functions that are replaced by Gnulib on Win32
>> call set_winsock_errno. This function reads the error from winsock
>> (WSAGetLastError) and sets errno to
I'm being told that there is a free development environment called CeGCC [2].
Both the Microsoft development environment and this one provide only a
rudimentary C library: according to [3] it has even less functions than
Windows, namely:
- no
- no
- no
- no
- no
- no
Care or d
On 11/26/2009 05:52 PM, Richard W.M. Jones wrote:
Currently any socket functions that are replaced by Gnulib on Win32
call set_winsock_errno. This function reads the error from winsock
(WSAGetLastError) and sets errno to some corresponding Unix-ish
approximation. The vast majority of functions
On Thu, 26. Nov 2009, 10:43:07 +0100, Bruno Haible wrote:
> Other updates that would be interesting - does someone of you have access to
> such a machine?
> - NetBSD 5.0
Sent privately.
Currently any socket functions that are replaced by Gnulib on Win32
call set_winsock_errno. This function reads the error from winsock
(WSAGetLastError) and sets errno to some corresponding Unix-ish
approximation. The vast majority of functions (non-socket ones) still
require you to deal with Ge
Bruno Haible wrote:
> Other updates that would be interesting - does someone of you have access to
> such a machine?
> - HP-UX 11.31
Sent offlist.
/haubi/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 11/26/2009 2:43 AM:
> Other updates that would be interesting - does someone of you have access to
> such a machine?
> - Cygwin 1.7
Sent privately.
- --
Don't work too hard, make some time for fun as well!
Eric Blake
Bruno Haible wrote:
>> That is because something[*] in your environment has arranged to ignore
>> SIGPIPE.
>
> The "ps s" output that I provided shows that SIGPIPE is being caught, not
> ignored, by the bash process. But I have no clue why I saw this error
> message only in an interactive bash and
Bruno Haible wrote:
> Jim Meyering wrote:
>> srcdir is expected to come from automake, and there, it is guaranteed
>> to be sanitized. It is usually simply "." or ".." or the name of a
>> package's subdirectory like "src" or "lib".
>
> But it can contain absolute directory names. For example, whe
Bruno Haible wrote:
> Jim Meyering wrote:
>> --- a/tests/init.sh
>> +++ b/tests/init.sh
>> @@ -27,6 +27,7 @@
>> # Note that these commands are executed in a subdirectory, therefore you
>> # need to prepend "../" to relative filenames in the build directory.
>> # Set the exit code 0 for suc
Jim Meyering wrote:
> --- a/tests/init.sh
> +++ b/tests/init.sh
> @@ -27,6 +27,7 @@
> # Note that these commands are executed in a subdirectory, therefore you
> # need to prepend "../" to relative filenames in the build directory.
> # Set the exit code 0 for success, 77 for skipped, or 1 o
Bruno Haible writes:
> Hi Simon,
>
>> > The question "which platforms support a given interface?" is, I think, best
>> > answered by the symbols x platforms matrix that I'm maintaining at
>> > http://www.haible.de/bruno/gnu/various-symlists.tar.gz
>>
>> Ah, that is probably more reliable. How
Jim Meyering wrote:
> srcdir is expected to come from automake, and there, it is guaranteed
> to be sanitized. It is usually simply "." or ".." or the name of a
> package's subdirectory like "src" or "lib".
But it can contain absolute directory names. For example, when I have a
package in /home/b
Hi Jim,
> I've avoided the diagnostic by changing the script
> not to write anything to the pipe:
Thanks.
> That is because something[*] in your environment has arranged to ignore
> SIGPIPE.
The "ps s" output that I provided shows that SIGPIPE is being caught, not
ignored, by the bash process.
Hi Simon,
> > The question "which platforms support a given interface?" is, I think, best
> > answered by the symbols x platforms matrix that I'm maintaining at
> > http://www.haible.de/bruno/gnu/various-symlists.tar.gz
>
> Ah, that is probably more reliable. How do I best generate the lists?
Eric Blake wrote:
> According to Bruno Haible on 11/25/2009 3:24 PM:
>> + # Note that these commands are executed in a subdirectory, therefore you
>> + # need to prepend "../" to relative filenames in the build dir.
>> + # Set the exit code 0 for success, 77 for skipped, or 1 or other for
>>
Bruno Haible wrote:
>> I want to use something like this for each of the tests I own ...
>> ...
>> I'll post some examples of using this new framework later today.
>
> One of the most important aspects of unit tests is that users are able to
> 1. execute a single test, rather than all tests,
>
Bruno Haible wrote:
> Hi Jim,
>
>> +test -f $srcdir/init.cfg \
>> + && . $srcdir/init.cfg
>
> Directory names containing spaces are not so uncommon, especially on Cygwin.
> How about writing "$srcdir/init.cfg" ?
>
> Likewise in test-pread.sh.
srcdir is expected to come from automake, and there,
21 matches
Mail list logo
