From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/800 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Wrapper scripts and Open64 Date: Thu, 3 May 2012 19:58:24 -0400 Message-ID: <20120503235824.GU14673@brightrain.aerifal.cx> References: <20120503132048.f4a26b72.idunham@lavabit.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1336089299 1546 80.91.229.3 (3 May 2012 23:54:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 3 May 2012 23:54:59 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-801-gllmg-musl=m.gmane.org@lists.openwall.com Fri May 04 01:54:59 2012 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 1SQ5rM-00037X-KN for gllmg-musl@plane.gmane.org; Fri, 04 May 2012 01:54:56 +0200 Original-Received: (qmail 18112 invoked by uid 550); 3 May 2012 23:54:56 -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 18104 invoked from network); 3 May 2012 23:54:55 -0000 Content-Disposition: inline In-Reply-To: <20120503132048.f4a26b72.idunham@lavabit.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:800 Archived-At: On Thu, May 03, 2012 at 01:20:48PM -0700, Isaac Dunham wrote: > I was curious, and started playing with Open64... > Open64 is at least as troublesome as gcc, but it doesn't work with > specfiles. > So if I use kopencc (the GCC-style wrapper that Open64 uses) instead > of gcc, the specfile version doesn't work...but the version from > commit 02eb568 does work. I'm surprised it works, since it was partly specfile based too. Are you sure everything at the linking stage was working (including inhibiting search of non-musl paths), and not just the compiler? > Open64 doesn't have stack-protector AFAIK. That shouldn't be a problem. > Open64 does require C++ to compile...as do most C++ compilers that > I've tried. > So how exactly do you bootstrap a C++ environment under musl? Building gcc 4.6.2 with C++ support and libstdc++ should work fine as long as you replace libstdc++/config/os/gnu-linux with generic to eliminate the poking at glibc locale internals. Once you have it working you should (in theory) be able to build other compilers written in C++... Rich