On Apr 23, 2010, at 3:04 PM, ext Paul Eggert wrote:
> Jarno Rajahalme writes:
>
>> So it seems that the aim is for the gnulib/stdint.h types and the
>> macros be consistent with the system versions. If so, why not use the
>> system versions for defining them, if they exist?
>
> Because the sys
Hi Ian,
> I've released a new stable snapshot. See attached NEWS.stable for details.
> Feedback welcome.
Thanks! I think it comes at the right time: The destabilizing changes for
C++ support, that started around 2010-03-07, are mostly stabilized by now.
Bruno
Hi,
Attached is a trivial patch to the top-level Makefile
to stop 'make check' generating an error when there is
no .git directory present (which will happen with the
stable snapshot tarball).
I've already applied this patch in the just-released stable snapshot.
cheers,
Ian.
--
Ian Beckwith -
--
* 20100424-stable
Snapshot taken based on:
commit ba564f2164f381af846d9695e6465cffe7ec918c
Date: Fri Apr 9 02:02:15 2010 +0200
with the following additional commits:
* [950f346]->[99a272b] ftruncate: mark module as obsolete; even MinGW
provides it,
Hi,
I've written a guide to creating stable snapshots, and a
script to help with the cherry-picking (both attached).
If you feel they are appropriate to be in the gnulib tree, feel free.
If so, would you prefer the guide in another format, eg texinfo?. If
not, well, they are now in the list archi
Hi,
I've released a new stable snapshot. See attached NEWS.stable for details.
Feedback welcome.
Tarball: http://erislabs.net/ianb/projects/gnulib/gnulib-20100424-stable.tar.gz
Gitweb: http://erislabs.net/gitweb?p=gnulib.git;a=shortlog;h=refs/heads/stable
Git: git://erislabs.net/gnulib.gi
Jarno Rajahalme wrote:
> These warnings only show with -O, so this is related to optimization.
>
> I have included the preprocessed output (main.cpp).
>
> Compiled with:
> g++-mp-4.4 -DHAVE_CONFIG_H -I.. -I../lib -O1 -E -dD -c -o main.cpp main.cc
Thanks. I've reduced this to a test case and repo
Hi Simon,
> Now the test-openpty self-test hangs on my Mac OS X machine, and the
> process doesn't even go away from the process table after a 'kill -9'.
> Here is a gdb session, which suggests it hangs when shutting down the
> process:
Strange. This program now uses the MacOS built-in openpty fu
Hi Simon,
> > It matters if you are asking to
> > print a 64-bit long, but passed a 32-bit int. To be safe, you should be
> > using 1L or even 1UL to match the %lx.
>
> My system is all 32-bit (debian i386 unstable). Using 1UL or even using
> a 'long int l = 12345' and passing that as a paramet
Hi,
Ian Beckwith wrote:
> printf-posix and fprintf-posix fail the test suite on debian stable and
> unstable, i386 and ia64.
>
> The problem seems to be the same, test-printf-posix2 and
> test-fprintf-posix2 fail at the same place. Looking at
> test-fprintf-posix2:
>
> gltests/test-fprintf-posix
Simon Josefsson wrote:
> Adding AC_PROG_CXX to gltests/configure.ac solves
> the problem. I see that ansi-c++-opt.m4 may be attempting to do setup a
> C++ compiler, but it doesn't seem to work when cross-compiling.
Well spotted! This should fix it:
2010-04-24 Bruno Haible
ansi-c++-o
Pádraig Brady wrote:
> The awkward macro is required to suppress warnings.
> I've asked gcc to relax that particular warning as referenced here:
> http://www.pixelbeat.org/programming/gcc/auto_init.html
In July 2008, the only reply to your request said "Please fill a bugzilla
PR so that it is not
On 23/04/10 23:51, Paul Eggert wrote:
I believe there is a bunch of places in gnulib which uses memset(P, 0,
sizeof(P)) to initialize structures containing pointers, which wouldn't
be OK if this is not the case.
>>>
>>> However, GNU Coding Standards states that we can assume that all
Hi Eric,
> For platforms without stdio hooking
These include AIX, HP-UX, IRIX, OSF/1, Solaris, mingw!
> the simplest thing we could think
> of is to create a temporary file under the hood, then provide gnulib
> overrides of fflush and fclose (the only two points at which POSIX
> requires that
Eric Blake wrote:
> The libvirt project would be very interested in using open_memstream,
And many other people, I'm sure, once they learn that
it exists and can be used portably.
> since it is now part of POSIX 2008. We even tossed around an idea
> on IRC on how to implement it for mingw, detai
Giuseppe Scrivano wrote:
> A small patch.
Looks good. I've pushed it, even though I didn't test it.
I presume you did.
Thanks.
...
> +2010-04-24 Giuseppe Scrivano
> +
> + vc-list-files: Add support for subversion
> + * build-aux/vc-list-files: Use "svn list" to generate the list of
>
Eric Blake wrote:
> + open_memstream-tests: new module
> + * modules/open_memstream-tests: New file.
I would mark it as an unportable test, like this:
Status:
unportable-test
The reason is that there are (so far) 7 types of stdio implementations:
- FreeBSD, NetBSD, OpenBSD, DragonF
Eric Blake wrote:
> Portability problems fixed by Gnulib:
> @itemize
> +...@item
> +This function is missing on some platforms:
> +MacOS X 10.3, FreeBSD 6.0, NetBSD 3.0, OpenBSD 3.8.
> @end itemize
Interix 3.5 can be added to this list; it also has the 'funopen' function.
Bruno
18 matches
Mail list logo
