[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnulib] Multiple definitions of symbol _xalloc_die
From: |
Bruno Haible |
Subject: |
Re: [Bug-gnulib] Multiple definitions of symbol _xalloc_die |
Date: |
Fri, 15 Oct 2004 15:45:34 +0200 |
User-agent: |
KMail/1.5 |
Simon Josefsson wrote:
> Do you know if there is a solution to this?
You could avoid linking with ext.o.
But probably it's better to think about the situation:
- Is libgss an application or a library? If it is a library, do the
application authors want their application to crash with a core dump
(after abort()) when memory is tight? (E.g. do you want your browser
or text editor to crash because of a problem in a library?)
- Is the desired memory allocation failure behaviour always the same
for all possible users of libshishi? Or does it depend on the application
that uses libshishi? In the latter case, what's the API through which
the application installs the error handler?
- Same question for libgss.
Bruno
- [Bug-gnulib] Multiple definitions of symbol _xalloc_die, Simon Josefsson, 2004/10/15
- Re: [Bug-gnulib] Multiple definitions of symbol _xalloc_die,
Bruno Haible <=
- [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Simon Josefsson, 2004/10/15
- Re: [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Bruno Haible, 2004/10/15
- [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Simon Josefsson, 2004/10/15
- [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Bruno Haible, 2004/10/15
- [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Simon Josefsson, 2004/10/15
- Re: [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Bruno Haible, 2004/10/15
- [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Simon Josefsson, 2004/10/15
- Re: [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die, Bruno Haible, 2004/10/15