From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11060 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl-cross-make build script. Date: Sat, 18 Feb 2017 13:53:01 +0100 Message-ID: <20170218125301.GK12395@port70.net> References: <20170217115321.GH12395@port70.net> <3fa40871-36f0-9d82-6602-f929ece76de6@se-instruments.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1487422402 10989 195.159.176.226 (18 Feb 2017 12:53:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 18 Feb 2017 12:53:22 +0000 (UTC) User-Agent: Mutt/1.6.0 (2016-04-01) Cc: musl To: Rob Landley Original-X-From: musl-return-11075-gllmg-musl=m.gmane.org@lists.openwall.com Sat Feb 18 13:53:16 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cf4Vi-0001yh-Ts for gllmg-musl@m.gmane.org; Sat, 18 Feb 2017 13:53:10 +0100 Original-Received: (qmail 19991 invoked by uid 550); 18 Feb 2017 12:53:14 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 19964 invoked from network); 18 Feb 2017 12:53:13 -0000 Mail-Followup-To: Rob Landley , musl Content-Disposition: inline In-Reply-To: <3fa40871-36f0-9d82-6602-f929ece76de6@se-instruments.com> Xref: news.gmane.org gmane.linux.lib.musl.general:11060 Archived-At: * Rob Landley [2017-02-18 02:45:38 -0600]: > On 02/17/2017 05:53 AM, Szabolcs Nagy wrote: > > i didnt know about -j$(nproc), what does it do? > > You answered your own question, but I note you can go "taskset 1 > ./thingy.sh" to do a single processor build with this. :) nice > >> for i in i686:: \ > >> armv5l:eabihf:--with-arch=armv5t armv7l:eabihf:--with-arch=armv7-a \ > >> "armv7m:eabi:--with-arch=armv7-m --with-mode=thumb --disable-libatomic --enable-default-pie" \ > >> armv7r:eabihf:--with-arch=armv7-r \ > >> armv8l:eabihf:--with-arch=armv8-a i486:: sh2eb:fdpic:--with-cpu=mj2 \ > >> mipsel:: mips:: powerpc:: sh4:: microblaze:: mips64:: powerpc64:: \ > >> s390x:: x86_64:: > > > > aarch64 is missing > > In theory armv8l is what they used to call aaaarrcchh64 before they > decided to stutter and pretend it wasn't arm or whatever that nonsense > is. (I've done my best to ignore it.) > > https://www.arm.com/products/processors/armv8-architecture.php > > In practice I haven't tested that one yet and it looks like it's broken, > have to figure out how to hit it with a rock... > > (The armv7r target is also broken because it's nommu but not pie, need > to tweak that...) > > > (and i don't think it's useful to > > build both armv7l and armv8l toolchains: the former > > can produce binaries for armv8-a targets just fine > > These are not multilib toolchains. If armv7l is 32 bit, armv8l is 64 > bit, they have different libgcc.a and so on... > > > and i don't know about any code in the toolchain target > > libs that would be different on armv8-a, > > One is 32 bit, one is 64 bit? > no, in a triplet "armv8" means the armv8 architecture in 32bit execution state (which arm calls aarch32) and that is backward compatible (and almost identical to) armv7 (at least the -a profile, armv8-m and armv7-m have more differences afaik) in a triplet "aarch64" means the armv8 architecture in 64bit execution state. so if you configure for armv8l-linux-musleabihf you get a toolchain that follows a 32bit arm abi and uses a 32bit arm isa (thumb or arm like with armv7). the 64bit triplet is aarch64-linux-musl (there is no soft float abi nor eabi suffix), there is an ilp32 abi for aarch64 which uses 64bit isa (like x32) which is not supported by musl, and a bigendian variant which can be configured with "aarch64_be" (but not used in practice i think).