Re: gnulib-tool changes

2005-09-05 Thread Bruno Haible
Simon Josefsson wrote: > There is a --symbolic parameter for gnulib-tool, so I thought copying > the files should be the default. > > Is this intentional? It was unintentional, and fixed last week too. Sorry. Bruno ___ bug-gnulib mailing list bug-gnu

Re: gnulib-tool changes

2005-09-03 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> >> It should default to 'libgnu' >> > >> > Yes. Fixed now as well. >> >> It doesn't seem to work: >> >> [EMAIL PROTECTED]:~/src/gnutls$ gnulib-tool --import --source-base=gl >> --m4-base=gl/m4 --lgpl getline error memmem getpass

Re: gnulib-tool changes

2005-09-02 Thread Bruno Haible
Simon Josefsson wrote: > >> It should default to 'libgnu' > > > > Yes. Fixed now as well. > > It doesn't seem to work: > > [EMAIL PROTECTED]:~/src/gnutls$ gnulib-tool --import --source-base=gl > --m4-base=gl/m4 --lgpl getline error memmem getpass minmax snprintf memmove > readline gnulib-tool: ***

Re: gnulib-tool changes

2005-09-02 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: >> [EMAIL PROTECTED]:~/src/gnutls$ gnulib-tool --import --macro-prefix=lgl >> --source-base=lgl --m4-base=lgl/m4 memmem gnulib-tool: *** missing --lib >> option >> gnulib-tool: *** Stop. >> [EMAIL PROTECTED]:~/src/gnutls$ >> >> It should default to 'libgnu'

Re: gnulib-tool changes

2005-09-01 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Fixed now. ... > Yes. Fixed now as well. ... >> What are these *.tmp files? > > The contain the contents of the file to install. Forgot to remove them. > Now also fixed. Thanks! >> lgl/Makefile.am:18: required file `lgl/memmove.c' not found >> lgl/Makef

Re: gnulib-tool changes

2005-09-01 Thread Bruno Haible
Simon Josefsson wrote: > I'll use GnuTLS as the test subject for this. First impressions: > > [EMAIL PROTECTED]:~/src/gnutls$ gnulib-tool --import > gnulib-tool: *** missing --source-base option > gnulib-tool: *** Stop. > [EMAIL PROTECTED]:~/src/gnutls$ > > That used to work Fixed now. > Then I

Re: gnulib-tool changes

2005-09-01 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Yup, I'm using two configure.ac's in gsasl, but I don't want to change >> gnutls to use the same scheme for only this reason. And with your >> work, I don't have to. > > OK, can you try it? The essential changes are already in C

Re: gnulib-tool changes

2005-09-01 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Yup, I'm using two configure.ac's in gsasl, but I don't want to change >> gnutls to use the same scheme for only this reason. And with your >> work, I don't have to. > > OK, can you try it? The essential changes are already in C

Re: gnulib-tool changes

2005-09-01 Thread Bruno Haible
Simon Josefsson wrote: > Yup, I'm using two configure.ac's in gsasl, but I don't want to change > gnutls to use the same scheme for only this reason. And with your > work, I don't have to. OK, can you try it? The essential changes are already in CVS. > >> How about storing the parameters in the

Re: gnulib-tool changes

2005-09-01 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Yay! I considered dropping use of gnulib in libgnutls yesterday, >> because I wanted the error module for the tools, but that module need >> a program_name variable. When the library didn't provide one, there >> were linker fai

Re: gnulib-tool changes

2005-08-31 Thread Bruno Haible
Simon Josefsson wrote: > Yay! I considered dropping use of gnulib in libgnutls yesterday, > because I wanted the error module for the tools, but that module need > a program_name variable. When the library didn't provide one, there > were linker failures. I added a dummy 'char *program_name = "g

Re: gnulib-tool changes

2005-08-31 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > 2) Support for multiple gnulib directories with a single configure.ac. > > It happens that a project wants to use gnulib in different parts, sometimes > even with different licenses, but these parts share the same config.h and > therefore the same configu