[Bug-gnulib] Re: Multiple definitions of symbol _xalloc_die

[Simon Josefsson]

Bruno Haible <address@hidden> writes:

> 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.

That could break the multiple-gnulib-instantiations-in-one-project
feature [*] I want.  Or at least there would have to be some
additional mechanism to apply the -D's at the right place.  A'la:

 gl_INIT([xalloc strdup dummy ...],
             [source_base=lgl; lib=liblgl; license=LGPL, xalloc_prefix=lgl],
         [xalloc error getopt progname ...],
             [source_base=gl; lib=libgl, xalloc_prefix=gl])

Then, the developer would have to implement gl_xalloc_die and
lgl_xalloc_die elsewhere.

Thanks.

[*] I was hoping to have it ready during this week, but I hadn't time.
And now I'm going on vacation for a week...  I'll do it when I get
back.