From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3107 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Request for ideas on arch-specific musl-gcc specfile additions Date: Sun, 14 Apr 2013 21:31:54 -0400 Message-ID: <20130415013154.GA7440@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 X-Trace: ger.gmane.org 1365989525 32616 80.91.229.3 (15 Apr 2013 01:32:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Apr 2013 01:32:05 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3111-gllmg-musl=m.gmane.org@lists.openwall.com Mon Apr 15 03:32:09 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 1URYHA-0006Da-C3 for gllmg-musl@plane.gmane.org; Mon, 15 Apr 2013 03:32:08 +0200 Original-Received: (qmail 7644 invoked by uid 550); 15 Apr 2013 01:32:07 -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 7636 invoked from network); 15 Apr 2013 01:32:07 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3107 Archived-At: Right now, musl-gcc has problems on at least a few archs: - powerpc: it does not setup the right secure-plt options for dynamic linking. - mips: gcc's internals on mips expect the -EL and -EB options to work for selecting endianness, but they're not real options; they're created by the specfile - any arch with 32/64-bit variants: if -m32 or -m64 was used building musl, it should get added to the specfile for musl-gcc. I'm looking for a clean approach to fixing this. Certainly the configure script could just generate one or more extra variables that get stored in config.mak and substituted into the specfile, but I'd rather avoid having essential logic like this in configure, as it makes it difficult for anybody who wants to generate config.mak by hand. If there are specific options always needed on a given arch, the build process (even without configure being used) should automatically add them to the specfile. Any good proposals? Rich