[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die
From: |
Bruno Haible |
Subject: |
Re: [Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die |
Date: |
Fri, 15 Oct 2004 21:27:03 +0200 |
User-agent: |
KMail/1.5 |
Simon Josefsson wrote:
> If the linker compare object code, it sounds inevitable that linking a
> program with two of my libraries that use gnulib will fail. Library X
> may use gnulib version from date X', but library Y use gnulib from
> date Y', so the code could differ. So if the linker compare object
> code, and refuse to link the library when there is a collision, things
> will be bad.
>
> But '-Dxalloc_die=$PROJECT_xalloc_die' sounds like a simple solution
> to the symptom I'm seeing now.
Someday we might even generate this list of -D flags automatically.
What would be needed is a list of global-scoped symbols per modules.
The format of modules/* could be extended to contain it.
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, 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
- [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 <=
- [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