Re: stdint generation

Hello Ralf, Thanks for explaining how this can work. I didn't know that "config.status --file=..." was applicable also to files that are not mentioned by AC_CONFIG_FILES. Ralf Wildenhues wrote: > you'd go to: > > # We need the following in order to create when the system > # doesn't have on

Re: stdint generation

Hello Bruno, * Bruno Haible wrote on Mon, Oct 15, 2007 at 09:19:01PM CEST: > Sam Steingold wrote: > > gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating > > stdint.h from stdint_.h, > > why do I need to maintain the sed command by hand? > > why can't this be done by config.status

Re: integrating gnulib into GNU clisp (was: Re: stdint generation)

Sam Steingold wrote: > > gnulib-tool --import --source-base=src/gllib --m4-base=src/glm4 \ > >--aux-dir=src/build-aux --no-changelog \ > >stdint stdbool ... > > this printed > > gnulib-tool: module config.guess doesn't exist > gnulib-tool: module

Re: stdint generation

Bruno Haible wrote: Sam Steingold wrote: gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating stdint.h from stdint_.h, why do I need to maintain the sed command by hand? why can't this be done by config.status? Two answers: Regarding the integration in GNU clisp: Since 2004, w

Re: stdint generation

Bruno Haible wrote: Sam Steingold wrote: gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating stdint.h from stdint_.h, why do I need to maintain the sed command by hand? why can't this be done by config.status? Two answers: Regarding the integration in GNU clisp: Since 2004, w

Re: stdint generation

On Oct 15, 2007, at 10:28 PM, Bruno Haible wrote: Sam Steingold wrote: gnulib-tool --import --source-base=src/gllib --m4-base=src/glm4 \ --aux-dir=src/build-aux --no-changelog \ stdint stdbool ... This will create a Makefile.am in src/gllib; there

Re: stdint generation

Sam Steingold wrote: > > gnulib-tool --import --source-base=src/gllib --m4-base=src/glm4 \ > >--aux-dir=src/build-aux --no-changelog \ > >stdint stdbool ... > > do I need to do this before each release? It's a good idea to do it, say, two weeks be

Re: stdint generation

Sam Steingold wrote: > gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating > stdint.h from stdint_.h, > why do I need to maintain the sed command by hand? > why can't this be done by config.status? Two answers: Regarding the integration in GNU clisp: Since 2004, when gnulib took

stdint generation

gnulib/gnulib/m4/stdint offers a multi-line sed rule for generating stdint.h from stdint_.h, why do I need to maintain the sed command by hand? why can't this be done by config.status? the same issue with stdbool...