From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3763 Path: news.gmane.org!not-for-mail From: Rob Landley Newsgroups: gmane.linux.lib.musl.general Subject: Re: C++ ABI compatibility and musl-gcc Date: Sat, 27 Jul 2013 01:04:00 -0500 Message-ID: <1374905040.3031.33@driftwood> References: <20130724232141.GA6531@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; DelSp=Yes; Format=Flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1374905053 16935 80.91.229.3 (27 Jul 2013 06:04:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 27 Jul 2013 06:04:13 +0000 (UTC) Cc: musl@lists.openwall.com To: musl@lists.openwall.com Original-X-From: musl-return-3767-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jul 27 08:04:15 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 1V2xbx-0007yA-GP for gllmg-musl@plane.gmane.org; Sat, 27 Jul 2013 08:04:13 +0200 Original-Received: (qmail 21994 invoked by uid 550); 27 Jul 2013 06:04:12 -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 21986 invoked from network); 27 Jul 2013 06:04:12 -0000 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:subject:to:cc:references:in-reply-to:x-mailer:message-id :mime-version:content-type:content-disposition :content-transfer-encoding:x-gm-message-state; bh=Z0xmyMGS397P0RwTMxeSRukuBc/fIqe3QTBGCAkBvVo=; b=T5WNqZtL+ZJKt9qbmJ4+cij3Av88rjSHmXNLvc1UemZg5rF2d9DrCLLO/2IvPjwedJ oTferwwv57/sb7wzQj7EJXtkJFqNJDQ6Vq1EKp0tzq3IBwBU7cWsBGiEzabeiqixdM0K r7Qu4X+xJjeLfc3kGQap2ug840RqQg8DcycHRqwGqirvzeZSkF+gLFcTRJ/27RPrPtKY O13M+RQauUTVSFrpmSDIaTpkL4U0AweGnKHvDypdKiHEMFsk48JsAq0Q07AQ5hk81EY3 XtN59NuId54vfyjmtYYAe7bP9Nj+1K5XtU/ClHw+WOlBgbOUWsgB/QorW2yr/HXjlH4s zs7w== X-Received: by 10.182.120.196 with SMTP id le4mr45230769obb.57.1374905040647; Fri, 26 Jul 2013 23:04:00 -0700 (PDT) In-Reply-To: <20130724232141.GA6531@brightrain.aerifal.cx> (from dalias@aerifal.cx on Wed Jul 24 18:21:41 2013) X-Mailer: Balsa 2.4.11 Content-Disposition: inline X-Gm-Message-State: ALoCoQkU72KrbnoUKzRPmvbd3qp5MeMQ5I01kOs6DSYdtkiUNHp1R2tS8xKGLmDKhLgwhCeHaCQT Xref: news.gmane.org gmane.linux.lib.musl.general:3763 Archived-At: On 07/24/2013 06:21:41 PM, Rich Felker wrote: > I've just committed the last of a series of changes that make it > possible to load the glibc-built libstdc++.so.6 under musl. While it > may look like a bit of ugliness, roughly half of the changes were > needed anyway to lay the ground for future locale support; the > long-term goal is to support customizable LC_TIME, LC_MONETARY, > LC_COLLATE, and LC_MESSAGES, but I don't expect any of that to happen > until after the 1.0 release. >=20 > Anyway, back to musl-gcc. My hope was that supporting the glibc > libstdc++ would make it possible to use musl-gcc to compile C++ code, > which could in turn be useful for bootstrapping compilers written in > C++ (gcc 4.8 or clang/LLVM). However, it seems the installed C++ > headers are also full of glibc-header-specific assumptions, so using > musl-gcc for C++ is not as easy as I'd hoped it might be. >=20 > I''ve already spent a great deal of time and effort onthis C++ ABI > topic and would rather focus on release prep and other issues for a > while now. But perhaps someone interested in this topic could do some > research and see if the idea of using musl-gcc for C++ can be > salvaged. Here are some possible approaches: >=20 > 1. Figuring out what's wrong with the headers and working around it. > Or, in other words: >=20 > lets write a musl-fixincludes :P >=20 > 2. Determining if the C++ headers that result from building a > musl-targetted libstdc++ are clean and arch-agnostic, and if so, > just packaging them up in a tarball that users could download and > install. If you're ever in Pittsburgh, I know the guy who wrote uClibc++. The current one has a lot of gpl code copied from glibc (headers =20 mostly, same as uClibc), and he stopped working on it when I dinged him =20 about copying GPLv3 code into an attempted update and he didn't know =20 how to proceed from there. (And was largely losing interest in hobby =20 programming now that he has a programming day job; he did it while he =20 was working the night shift managing a hotel.) But if anybody knows "what's involved in implementing libstdc++", it =20 would be somebody who did. :) Rob=