Re: [PATCH] README-release improvements

Hi Stefano, On 23 Oct 2011, at 00:20, Stefano Lattarini wrote: > Hi everybody. Just my two cents about this matter ... > > On Saturday 22 October 2011, Bruno Haible wrote: >> Gary V. Vaughan wrote: > Running the (potentially) outdated configure, to build a (potentially) > outdated Makefi

Re: porting to NeXTstep

On Sat, 2011 Oct 22 14:41+0200, Bruno Haible wrote: > > Good point. And adding EILSEQ in errno.in.h also requires a change to > lib/strerror-override.c. And a couple other places, I believe! Revised patch attached. --Daniel -- Daniel Richard G. || sk...@iskunk.org My ASCII-art .sig got a bad

Re: porting to NeXTstep

Sorry for the delay; didn't have time to revisit this till today. On Wed, 2011 Oct 19 11:23+0200, Bruno Haible wrote: > > The files m4/strcoll.m4, lib/strcoll.c, modules/strcoll, > m4/string_h.m4, lib/string.in.h, modules/string, > doc/posix-functions/strcoll.texi > are probabl

Re: [PATCH] README-release improvements

On Saturday 22 October 2011, Jim Meyering wrote: > Stefano Lattarini wrote: > >> make -k maintainer-clean # Clean up previous build artefacts > >> ./configure > >> make maintainer-clean# Clean up previous build artefacts > >> git checkout master > >> git pull origin master # don't t

Re: [PATCH] README-release improvements

Stefano Lattarini wrote: > Hi everybody. Just my two cents about this matter ... > > On Saturday 22 October 2011, Bruno Haible wrote: >> Gary V. Vaughan wrote: >> > >> Running the (potentially) outdated configure, to build a (potentially) >> > >> outdated Makefile, which may very well rerun acloc

Re: [PATCH] README-release improvements

Hi everybody. Just my two cents about this matter ... On Saturday 22 October 2011, Bruno Haible wrote: > Gary V. Vaughan wrote: > > >> Running the (potentially) outdated configure, to build a (potentially) > > >> outdated Makefile, which may very well rerun aclocal, automake, autoconf > > >> etc

Re: [PATCH] README-release improvements

Gary V. Vaughan wrote: ... > Okay to push? Yes, but with the following changes applied: use this instead, per today's discussion: make -k maintainer-clean || { ./configure && make maintainer-clean; } and change "incase" to "in case" in the commit log and ChangeLog: > readme-release: several

Re: Redefinition of errno constants in MSVC10

Hi, Michael Goffioul wrote: > When trying to compile current octave with MSVC10, I get a bunch of > macro redefinition in errno.h module. See the following from the > involved headers: > > $ grep ECONNRESET errno.h > # define ECONNRESET 10054 > > $ grep ECONNRESET /c/Program\ Files/Microso

Re: [PATCH] README-release improvements

Hi Jim, > > ./configure > > make maintainer-clean# Clean up previous build artefacts > > What's the point of rerunning configure and maintainer-clean? I sometimes do "make distclean" in a subdirectory. This removes some but not all Makefiles. "make -k maintainer-clean" will thus fail and

Re: [PATCH] README-release improvements

Bruno Haible wrote: > Gary V. Vaughan wrote: >> >> Running the (potentially) outdated configure, to build a (potentially) >> >> outdated Makefile, which may very well rerun aclocal, automake, autoconf >> >> etc just to call the maintainer-clean rule, and then blow it all away >> >> in the next step

Re: porting to NeXTstep

Hi Daniel, > * Tacked on "&& !defined __NeXT__" in lib/stdio.in.h. Easier than adding > a separate test for asm-label functionality, anyway. I don't remember: What is the version of NeXT gcc? Does it support the __attribute__ __format__ __printf__ syntax? extern int printf (const char *forma

Re: perror.m4 test

Eric Blake wrote: > > I'm not sure. This test is about perror(). Should it fail just because > > strerror returns an invalid pointer? Eric, what do you think? > > perror() is required to give output containing the same string as > strerror, and strerror() is required to give a valid string (possi

Re: [PATCH] perror: test for output mismatch

Eric Blake wrote on 2011-06-21: > diff --git a/ChangeLog b/ChangeLog > index 07f3819..36d72ae 100644 > --- a/ChangeLog > +++ b/ChangeLog > @@ -1,5 +1,9 @@ > 2011-06-21 Eric Blake > > + perror: test for output mismatch > + * m4/perror.m4 (gl_FUNC_PERROR): Add test, in order to replace >

Re: [PATCH] README-release improvements

Hi Jim, On 22 Oct 2011, at 17:15, Jim Meyering wrote: > Gary V. Vaughan wrote: >> >> If you want to clean the cruft out of your working directories before >> starting the release process, you should do it before you change branches >> and merge changes from upstream, using the Makefile that you a

Re: signbit #define'd causes compilation error in octave

Eric Blake wrote: > in C++, we could avoid the macros and > instead have three overloaded functions named signbit which operate on > the correct types, so as not to pollute the namespace with a macro. > POSIX does not speak to C++ compliance, so using overloads instead of a > macro for C++ does

Re: [PATCH] README-release improvements

Hi Jim, Gary V. Vaughan wrote: > >> Running the (potentially) outdated configure, to build a (potentially) > >> outdated Makefile, which may very well rerun aclocal, automake, autoconf > >> etc just to call the maintainer-clean rule, and then blow it all away > >> in the next step with a bootstrap

Re: [PATCH] README-release improvements

Gary V. Vaughan wrote: > Hi Jim, > > On 22 Oct 2011, at 03:06, Jim Meyering wrote: >> Gary V. Vaughan wrote: >>> As it stands (without this patch), README-release recommends: >>> >>> git checkout master >>> git pull >>> ./configure >>> make maintainer-clean >>> ./bootstrap >>> >>> Running the

Re: [PATCH] README-release improvements

Hi Jim, On 22 Oct 2011, at 03:06, Jim Meyering wrote: > Gary V. Vaughan wrote: >> As it stands (without this patch), README-release recommends: >> >> git checkout master >> git pull >> ./configure >> make maintainer-clean >> ./bootstrap >> >> Running the (potentially) outdated configure, to