I am forwarding an error reported on the inetutils mailing list.
The problem is that readline 6.x exports `xmalloc' and `xrealloc', and
it causes a linker error when used together with gnulib.
Probably readline shouldn't export these symbols, but I think it should
be possible
Alfred M. Szmidt a...@gnu.org ha escrit:
This is a known bug, the reason if I recall is that readline exports
xmalloc and xrealloc is to allow programs to hook their own version
into readline. So the readline maintainer has declined any fixes for
this.
This is a severe bug. It makes
This is a known bug, the reason if I recall is that readline
exports xmalloc and xrealloc is to allow programs to hook their
own version into readline. So the readline maintainer has
declined any fixes for this.
This is a severe bug. It makes readline useless for any project
On 7/25/10 10:33 AM, Alfred M. Szmidt wrote:
This is a known bug, the reason if I recall is that readline
exports xmalloc and xrealloc is to allow programs to hook their
own version into readline. So the readline maintainer has
declined any fixes for this.
This is a
xmalloc etc. are commonly used names in GNU applications, regardless of
whether the apps are gnulib-based; for example, Emacs and GCC both have
their own xmalloc, independent of gnulib. It would be nicer if readline
were compatible with this common usage, without application developers
having to
On 7/25/10 2:38 PM, Paul Eggert wrote:
xmalloc etc. are commonly used names in GNU applications, regardless of
whether the apps are gnulib-based; for example, Emacs and GCC both have
their own xmalloc, independent of gnulib. It would be nicer if readline
were compatible with this common
On 7/25/10 2:36 PM, Mike Frysinger wrote:
why do you need to use those function names ? using a name spaced function
like rl_malloc or _rl_malloc would keep the same functionality without
clashing with other people.
No, it wouldn't. It would not allow, for instance, an application to
On 7/25/10 2:00 PM, Chet Ramey wrote:
On 7/25/10 10:33 AM, Alfred M. Szmidt wrote:
This is a known bug, the reason if I recall is that readline
exports xmalloc and xrealloc is to allow programs to hook their
own version into readline. So the readline maintainer has
declined
On Sunday, July 25, 2010 17:18:02 Chet Ramey wrote:
On 7/25/10 2:36 PM, Mike Frysinger wrote:
why do you need to use those function names ? using a name spaced
function like rl_malloc or _rl_malloc would keep the same functionality
without clashing with other people.
No, it wouldn't.
Hello,
I am forwarding an error reported on the inetutils mailing list.
The problem is that readline 6.x exports `xmalloc' and `xrealloc', and
it causes a linker error when used together with gnulib.
Probably readline shouldn't export these symbols, but I think it should
be possible somehow to
Hi,
Giuseppe Scrivano wrote:
The problem is that readline 6.x exports `xmalloc' and `xrealloc', and
it causes a linker error when used together with gnulib.
According to what Chet Ramey said in
http://lists.gnu.org/archive/html/bug-readline/2009-06/msg3.html
it should be possible to
On 6/8/10 5:20 AM, Bruno Haible wrote:
Hi,
Giuseppe Scrivano wrote:
The problem is that readline 6.x exports `xmalloc' and `xrealloc', and
it causes a linker error when used together with gnulib.
According to what Chet Ramey said in
12 matches
Mail list logo
