From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 5D1EB1A1DFA for ; Tue, 9 Aug 2016 01:40:00 -0700 (PDT) Received: by mail-wm0-x22e.google.com with SMTP id q128so2960143wma.1 for ; Tue, 09 Aug 2016 01:40:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sGJx3KfKkKDReQ3LrlZHo3DcKYuLQjzh/GxOcgwGwss=; b=IB9l+0X3oovrGFMX6fmYErvy32LhlqDuXU5wttBqBoFqgbfsIGQP64TFlA5clZfbRK wq5b8Rd5y1CuLgGIWQOHlCBsWrnIfnjdaCparUZa9B+hd2EP9oQEzkDDg9TgYHt6ZZ+/ ViGOd8xo9XAkhvBp58U2N1mOyg3SI1XvJcJPM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=sGJx3KfKkKDReQ3LrlZHo3DcKYuLQjzh/GxOcgwGwss=; b=cTNFcjzpvqgLBrIsDSFIuit2kUmKbKJa8AYpQopaWUfrio7Fy7+jOa3vMwfK6d2Zni V7keVqbZFPL0fr1IjGYb0SGSgy1bNmJYrIlY345vvza2It8duzOGljrxSP0Ra/uQAKTe Cx1yVrhHg+83DoIN2D4kJmefRh8hqE5TJmvqPTpLHCOKk4goJVAoblIBpdbsawbpKkM/ OJFFBG3ACLlPkmZ0X4WA53tRgqTyJCHwB4LUMRzr+6A+ftpUgV3hXZj/w0IBzuAHFCuu zPcdSLzCF3dcAIRHlEVzjcssxw7s/J+5fTcjtcOyg4zE7j+vGxtF7vW21okiD5MI1WCR g9+w== X-Gm-Message-State: AEkoous2lXS+pPVcdVeTAXJsisQeFKyXJ/VNgmZMuNfWbD1rYDcZEYK8lEivQ3mZUT7hCePI X-Received: by 10.28.113.151 with SMTP id d23mr21534278wmi.89.1470731998708; Tue, 09 Aug 2016 01:39:58 -0700 (PDT) Received: from bivouac.eciton.net (bivouac.eciton.net. [2a00:1098:0:86:1000:23:0:2]) by smtp.gmail.com with ESMTPSA id pm1sm36706801wjb.40.2016.08.09.01.39.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Aug 2016 01:39:57 -0700 (PDT) Date: Tue, 9 Aug 2016 09:39:55 +0100 From: Leif Lindholm To: Michael Zimmermann Cc: valerij zaporogeci , edk2-devel , Ard Biesheuvel Message-ID: <20160809083955.GH31760@bivouac.eciton.net> References: MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: Toolchain question X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2016 08:40:00 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Aug 09, 2016 at 06:07:36AM +0200, Michael Zimmermann wrote: > As for the kind of toolchain to use: there's always (at least) two types: > bare metal toolchains(arm-eabi,arm-none-eabi, aarch64-elf), and the ones > with a OS ABI(androideabi, linux-gnueabi,linux-gnueabihf, ...). While > unlike other bootloader/kernel projects EDK2 seems to work with all of them > I can only recommend using the bare metal variants. > > For ARM and AArch64 I recommend using linaro's latest stable release(5.3 at > the time of writing): > http://www.linaro.org/downloads/ > sometimes the website is out of date and you can go here directly: > https://releases.linaro.org/components/toolchain/binaries/ So, while all of the above is fine, I only ever use the native compiler under Linux, or one of the linaro "-linux-" flavours if cross-compiling. I am however happy someone is testing the bare-metal profiles as well, since we need to keep the environment (i.e. build configuration) rigid enough that toolchain flavour does not affect things. > I've also CC'ed the Arm maintainers so you'll actually get answers unlike > me when I asked the same question about a year ago ;) Thanks :) Regards, Leif