[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnulib] Symbol collision
From: |
Bruno Haible |
Subject: |
Re: [Bug-gnulib] Symbol collision |
Date: |
Mon, 14 Jul 2003 15:44:36 +0200 |
User-agent: |
KMail/1.5 |
Simon Josefsson wrote:
> It occured to me that if some of these functions happen to be included
> in both libraries, e.g. strdup, won't linking an application to both
> libraries break? The same symbol would be defined by both libraries.
> I'm not sure if some linkers only treat this as a warning, instead of
> an error, but even this seem to be unwanted.
This is likely to be a problem with non-static *variables* on some
platforms (like MacOS X or Woe32). With *functions* I think all should
be fine if the two functions are equivalent.
Someone with access to MacOS X and Woe32 systems should verify this...
> (Using weak symbol definitions could work, but is this portable?)
Weak symbols are only supported by Solaris and glibc < 2.3.
Bruno