From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2550 Path: news.gmane.org!not-for-mail From: Isaac Dunham Newsgroups: gmane.linux.lib.musl.general Subject: Re: Remaining ABI issues Date: Thu, 10 Jan 2013 08:04:54 -0800 Message-ID: <20130110080454.95e3c126.idunham@lavabit.com> References: <20130110040319.GA5159@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1357833915 12102 80.91.229.3 (10 Jan 2013 16:05:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Jan 2013 16:05:15 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2551-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jan 10 17:05:31 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1TtKdB-0007Fy-46 for gllmg-musl@plane.gmane.org; Thu, 10 Jan 2013 17:05:25 +0100 Original-Received: (qmail 7242 invoked by uid 550); 10 Jan 2013 16:05:08 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7232 invoked from network); 10 Jan 2013 16:05:08 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=jT/1EwT9LzSAJ09Q7Vgb7NOT8VZZieI6SR4GGvTdm6Oml1yrnF6PrXbfoRahYxEg59/XrXe6opA/PtPJeF9l+vVqbt0EBCVgwz9A/HRZOg32t/jZFiIS5UpLv9q05ib5sXChySS/Xl2NVBfpFdaOa+5x6E0E32in8gOn6r4bGSA=; h=Date:From:To:Subject:Message-Id:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding; In-Reply-To: <20130110040319.GA5159@brightrain.aerifal.cx> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; i486-pc-linux-gnu) Xref: news.gmane.org gmane.linux.lib.musl.general:2550 Archived-At: On Wed, 9 Jan 2013 23:03:19 -0500 Rich Felker wrote: > As for type-2 issues (C++ ABI), there are a number I'm aware of and > probably plenty more I'm not aware of, where we don't match glibc and > thus can't work with glibc-targeted shared library binaries or > applications written in C++: > > - FILE, mbstate_t, and fpos_t tags don't match glibc's. Hmm...it cares about what FILE looks like? > - Underlying type of pthread_t is pointer in musl, long in glibc > > - Type of timer_t is a pointer in musl; this is actually > non-conforming to POSIX as well as being incompatible with glibc. FYI, I compared man 3posix types.h (SUSv3) with the POSIX 2008 description, and it looks like the use of a pointer for pthread_t was at one point not permitted, though this was fixed by POSIX 2004. > - Not only do the struct tags underlying jmp_buf and sigjmp_buf > mismatch glibc's; worse, glibc uses the SAME tag for both (i.e. > they're the same type). -- Isaac Dunham