Re: Opening a can of worms: a readline gnulib module?

"Oskar Liljeblad" <[EMAIL PROTECTED]> writes: > On Thursday, August 11, 2005 at 23:14, Simon Josefsson wrote: >> >> > I don't know if the readline module covers this, but on recent >> > Fedora/RedHat systems you'll need to link with ncurses or some >> > other library providing certain termcap (or

Re: Opening a can of worms: a readline gnulib module?

On Thursday, August 11, 2005 at 23:14, Simon Josefsson wrote: > > > I don't know if the readline module covers this, but on recent > > Fedora/RedHat systems you'll need to link with ncurses or some > > other library providing certain termcap (or was it terminfo?) > > functions... You don't need to

Re: Opening a can of worms: a readline gnulib module?

"Oskar Liljeblad" <[EMAIL PROTECTED]> writes: > I don't know if the readline module covers this, but on recent > Fedora/RedHat systems you'll need to link with ncurses or some > other library providing certain termcap (or was it terminfo?) > functions... You don't need to do this with Debian. Thi

Re: Opening a can of worms: a readline gnulib module?

Bruno Haible <[EMAIL PROTECTED]> writes: >> > HAVE_READLINE vs. HAVE_READLINE_READLINE_H should be the same. >> >> I solved it slightly differently. I made these two tests orthogonal. >> readline/readline.h is used by the header file if available. >> -lreadline is used instead of the *.c file if

Re: Opening a can of worms: a readline gnulib module?

Simon Josefsson wrote: > Installed the patch below. Thanks a lot. (This stuff is not a piece of cake.) > > HAVE_READLINE vs. HAVE_READLINE_READLINE_H should be the same. > > I solved it slightly differently. I made these two tests orthogonal. > readline/readline.h is used by the header file if a

Re: Opening a can of worms: a readline gnulib module?

I don't know if the readline module covers this, but on recent Fedora/RedHat systems you'll need to link with ncurses or some other library providing certain termcap (or was it terminfo?) functions... You don't need to do this with Debian. Regards, Oskar

Re: Opening a can of worms: a readline gnulib module?

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> So the entire M4 file read as below now. Correct? > > gl_cv_lib_readline vs. ac_cv_lib_readline_readline should be the same. > HAVE_READLINE vs. HAVE_READLINE_READLINE_H should be the same. I solved it slightly differently. I

Re: Opening a can of worms: a readline gnulib module?

Simon Josefsson wrote: > So the entire M4 file read as below now. Correct? gl_cv_lib_readline vs. ac_cv_lib_readline_readline should be the same. HAVE_READLINE vs. HAVE_READLINE_READLINE_H should be the same. After this, you can commit it if it works. Let's see whether it also needs mention of l

Re: lgpl compatible files archive?

On Thu, Aug 11, 2005 at 08:20:42PM +0200, Simon Josefsson wrote: > Albert Chin <[EMAIL PROTECTED]> writes: > > > I'm in need of this for strtoll() in wget which isn't available on > > HP-UX. However, wget has the OpenSSL exception to the GPL and I don't > > want to import strtoll and invalidate th

Re: lgpl compatible files archive?

Albert Chin <[EMAIL PROTECTED]> writes: > On Sun, Jul 03, 2005 at 01:11:05PM -0700, Paul Eggert wrote: >> Patrice Dumas <[EMAIL PROTECTED]> writes: >> >> > I am currently packaging a library under the LGPL, so I cannot use the >> > files >> > of the gnulib that are under the GPL. Is there somewh

Re: lgpl compatible files archive?

On Sun, Jul 03, 2005 at 01:11:05PM -0700, Paul Eggert wrote: > Patrice Dumas <[EMAIL PROTECTED]> writes: > > > I am currently packaging a library under the LGPL, so I cannot use the files > > of the gnulib that are under the GPL. Is there somewhere a project similar > > with the gnulib but with fi

Re: Opening a can of worms: a readline gnulib module?

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> >> > + printf ("%s", prompt); >> > >> > You can simplify that to >> > >> > fputs (prompt); > > Oops, I meant: fputs (prompt, stdout). Sorry. Ah, added. >> +#include >> +#include >> + >> +/* Get specification. */ >> +#

Re: Opening a can of worms: a readline gnulib module?

> * Bruno Haible <[EMAIL PROTECTED]> [2005-08-11 16:46:35 +0200]: > >> > + AC_CHECK_LIB(readline, readline) > > Can you please use AC_LIB_LINKFLAGS (from lib-link.m4) instead? So > that the library is recognized (and the -rpath linker option is used) > when it is installed in the $PREFIX directory

Re: Opening a can of worms: a readline gnulib module?

Simon Josefsson wrote: > >> > + printf ("%s", prompt); > > > > You can simplify that to > > > > fputs (prompt); Oops, I meant: fputs (prompt, stdout). Sorry. > No, I don't want a newline. fputs() doesn't output an extra newline. Only puts() does. > +#include > +#include > + > +/* Get

Re: Opening a can of worms: a readline gnulib module?

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Any objections to this readline module? There were some discussion, >> but no real objection from what I could tell. > > There was the objection that some packages need more from GNU readline > than just one function. Therefore

Re: Opening a can of worms: a readline gnulib module?

Sam Steingold <[EMAIL PROTECTED]> writes: >> * Simon Josefsson <[EMAIL PROTECTED]> [2005-07-16 22:30:27 +0200]: >> >> * readline.m4: New file. > > please take a look at > http://cvs.sourceforge.net/viewcvs.py/*checkout*/clisp/clisp/src/m4/readline.m4 Is there a particular part of that file w

Re: Opening a can of worms: a readline gnulib module?

Simon Josefsson wrote: > Any objections to this readline module? There were some discussion, > but no real objection from what I could tell. There was the objection that some packages need more from GNU readline than just one function. Therefore you will need to add more functions upon demand :-)

Re: Opening a can of worms: a readline gnulib module?

> * Simon Josefsson <[EMAIL PROTECTED]> [2005-07-16 22:30:27 +0200]: > > * readline.m4: New file. please take a look at http://cvs.sourceforge.net/viewcvs.py/*checkout*/clisp/clisp/src/m4/readline.m4 -- Sam Steingold (http://www.podval.org/~sds) running w2k

Re: Opening a can of worms: a readline gnulib module?

Simon Josefsson <[EMAIL PROTECTED]> writes: > Initial attempt. Tested on one platform with and without the readline > library inside GNU SASL. Any objections to this readline module? There were some discussion, but no real objection from what I could tell. There were no further discussion afte

Re: strnlen.h needed?

Simon Josefsson wrote: > but now there is a comment in both strnlen.c and > strnlen.h. Should we remove one of them? No. We keep the comment in strnlen.h because that's where most users will look at (in case they are on a machine where "man strnlen" doesn't work). And the one in the .c file, we k

Re: xvasprintf: don't depend directly on xalloc-die

Bruno Haible <[EMAIL PROTECTED]> writes: >> Wasn't the point of separating xalloc-die from the xmalloc module to >> allow applications to supply its own xalloc_die function? > > Such applications can now use > > gnulib-tool --avoid=xalloc-die > > See http://lists.gnu.org/archive/html/bug-gnul

Re: strnlen.h needed?

Bruno Haible <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> Ok to install? strnlen is a GNU extension, according to libc manual. >> There were some discussion regarding strnlen.h, but the patch below >> has worked for me for a while. Any problems can be fixed later on. >> It seems corre