Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-03-16 Thread Sam Steingold
Eric Blake wrote: On 03/08/2010 11:34 AM, Sam Steingold wrote: Sam Steingold wrote: Alternatively, I would be reasonably happy with sed -i -e 's/_GL_ARG_NONNULL/GL_ARG_NONNULL/' arg-nonnull.h sed -i -e 's/_GL_WARN_ON_USE/GL_WARN_ON_USE/' warn-on-use.h similar to GL_LINK_WARNING in link-warning.

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-03-08 Thread Eric Blake
On 03/08/2010 11:34 AM, Sam Steingold wrote: > Sam Steingold wrote: >> >> Alternatively, I would be reasonably happy with >> sed -i -e 's/_GL_ARG_NONNULL/GL_ARG_NONNULL/' arg-nonnull.h >> sed -i -e 's/_GL_WARN_ON_USE/GL_WARN_ON_USE/' warn-on-use.h >> similar to GL_LINK_WARNING in link-warning.h. >

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-03-08 Thread Sam Steingold
Sam Steingold wrote: Alternatively, I would be reasonably happy with sed -i -e 's/_GL_ARG_NONNULL/GL_ARG_NONNULL/' arg-nonnull.h sed -i -e 's/_GL_WARN_ON_USE/GL_WARN_ON_USE/' warn-on-use.h similar to GL_LINK_WARNING in link-warning.h. So, any chance the constants in arg-nonnull.h & warn-on-use

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-03-02 Thread Sam Steingold
On 3/2/10, Sam Steingold wrote: > Sam Steingold wrote: > > > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & > warn-on-use.h in src/build-aux. > > > > So, any chance these files could be restored to their proper place in > gllib? Alternatively, I would be reasonably happy wit

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-03-02 Thread Sam Steingold
Sam Steingold wrote: I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & warn-on-use.h in src/build-aux. So, any chance these files could be restored to their proper place in gllib? This location causes me huge problems because these files are not covered by sed_transform_lib_

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-26 Thread Sam Steingold
Ralf Wildenhues wrote: * Sam Steingold wrote on Wed, Feb 24, 2010 at 01:15:13AM CET: On 2/23/10, Bruno Haible wrote: Autoconf requires it to be constant. You specify it through the AC_CONFIG_AUX_DIR macro. In other words, if you add to clisp/modules/syscalls/configure.ac the line AC_CON

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-25 Thread Sam Steingold
Eric Blake wrote: According to Sam Steingold on 2/23/2010 3:06 PM: > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & > warn-on-use.h in src/build-aux. > why aren't these files in the usual place (src/gllib), together with all > the other headers? Because the versions in

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-24 Thread Sam Steingold
Hi, On 2/24/10, Ralf Wildenhues wrote: > * Sam Steingold wrote on Wed, Feb 24, 2010 at 01:15:13AM CET: > > On 2/23/10, Bruno Haible wrote: > > > Autoconf requires it to be constant. You specify it through the > > > AC_CONFIG_AUX_DIR macro. In other words, if you add to > > > clisp/modules

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-24 Thread Ralf Wildenhues
Hello, * Sam Steingold wrote on Wed, Feb 24, 2010 at 01:15:13AM CET: > On 2/23/10, Bruno Haible wrote: > > Autoconf requires it to be constant. You specify it through the > > AC_CONFIG_AUX_DIR macro. In other words, if you add to > > clisp/modules/syscalls/configure.ac > > the line > > AC_C

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Sam Steingold
On 2/23/10, Bruno Haible wrote: > Sam Steingold wrote: > > I want to be able to add build_aux= to the $(MAKE) invocation > > so that the file arg-nonnull.h & warn-on-use.h are found in the right > place. > > > build_aux is not something that you can change via an environment variable. this

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Bruno Haible
Sam Steingold wrote: > I want to be able to add build_aux= to the $(MAKE) invocation > so that the file arg-nonnull.h & warn-on-use.h are found in the right place. build_aux is not something that you can change via an environment variable. Autoconf requires it to be constant. You specify it th

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Sam Steingold
On 2/23/10, Eric Blake wrote: > According to Sam Steingold on 2/23/2010 3:06 PM: > > >> > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & > >> > warn-on-use.h in src/build-aux. > >> > why aren't these files in the usual place (src/gllib), together with > all > >> > the

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Eric Blake
According to Sam Steingold on 2/23/2010 3:06 PM: >> > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & >> > warn-on-use.h in src/build-aux. >> > why aren't these files in the usual place (src/gllib), together with all >> > the other headers? >> >> Because the versions in src/

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Sam Steingold
Hi, On 2/23/10, Eric Blake wrote: > According to Sam Steingold on 2/23/2010 2:05 PM: > > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & > > warn-on-use.h in src/build-aux. > > why aren't these files in the usual place (src/gllib), together with all > > the other headers?

Re: arg-nonnull.h & warn-on-use.h in build-aux

2010-02-23 Thread Eric Blake
According to Sam Steingold on 2/23/2010 2:05 PM: > Hi, > I updated gnulib in clisp and gnulib-tool installed arg-nonnull.h & > warn-on-use.h in src/build-aux. > why aren't these files in the usual place (src/gllib), together with all > the other headers? Because the versions in src/build-aux are t