This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ABI compatibility for gconv modules

From: Mike Frysinger <vapier at gentoo dot org>
To: libc-alpha at sourceware dot org
Cc: Florian Weimer <fweimer at redhat dot com>
Date: Fri, 08 Aug 2014 09:52:27 -0400
Subject: Re: ABI compatibility for gconv modules
Authentication-results: sourceware.org; auth=none
References: <53E4A0C8 dot 4040004 at redhat dot com>

On Fri 08 Aug 2014 12:04:56 Florian Weimer wrote:
> Do we need to preserve ABI for gconv modules, or are they totally
> internal to libc and we can break the interface as we see fit?

considering the warning that is issued when you link statically, i'd say the 
policy has been that the ABI is private to glibc.  especially since you can't 
really link directly against them, and you shouldn't be dlopening them 
directly.

i'm not saying i'd be in favor of making the static situation saner, but i 
don't think locking the gconv ABI is the answer.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

Follow-Ups:
- Re: ABI compatibility for gconv modules
  - From: Rich Felker
- Re: ABI compatibility for gconv modules
  - From: Florian Weimer

References:
- ABI compatibility for gconv modules
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]