From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56720 invoked by alias); 25 Nov 2019 21:55:34 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 56712 invoked by uid 89); 25 Nov 2019 21:55:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=andrewdeanmicrosoftcom, sk:Andrew., Andrew.Dean@microsoft.com, andrew.dean@microsoft.com X-HELO: mail-vs1-f66.google.com Received: from mail-vs1-f66.google.com (HELO mail-vs1-f66.google.com) (209.85.217.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Nov 2019 21:55:32 +0000 Received: by mail-vs1-f66.google.com with SMTP id x21so11241506vsp.6 for ; Mon, 25 Nov 2019 13:55:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7PyMTL9hNdfzuBlqaC+oo9h/XPcO0rdhalrN0O1lVtw=; b=jvHXOQuABEckPWB0mkwPP7IKSVdplYPsFKF05wHptTBhAGTcEkH+RESXI5d5pf9Jaj stShG+9GPKLyj5+yZhTEmxrP+j9QkEB3AhziiX68srWBT12iRMJbpnYqRFAw2E9jbIhk m5l5ZlcWSV/Rc/RHYp+y3KKw7O1E9AFEC8tSDzmuDWz08v3EVbX0EX+J/rLnXUm6NEZk uRmw/x1Th1KgPHgiCdmYpR8vjYpPpnH2Za+x84gmAcwiV4HzYg8CuHWowwLAOA5WtmPw BP3ljUgAFZctsbenzcOeZWxfzJ5xdUI7KP3kTsM+otnwohN/vhV/2BNgGz/X9c3sUJVt +Aaw== MIME-Version: 1.0 References: <1ef307de-6952-40c1-6581-238a75f10fe0@linaro.org> In-Reply-To: From: Ramana Radhakrishnan Date: Mon, 25 Nov 2019 21:55:00 -0000 Message-ID: Subject: Re: [EXTERNAL] Re: How to test aarch64 when building a cross-compiler? To: Andrew Dean Cc: Adhemerval Zanella , gcc mailing list Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00215.txt.bz2 On Mon, Nov 25, 2019 at 9:43 PM Andrew Dean wrote: > > > > >>> I get errors like this: > > > >>> > > > >>> aarch64-glibc-linux-gnu-gcc: fatal error: cannot read spec file > > > >>> 'rdimon.specs': No such file or directory > > > >>> > > > >>> I can see that the rdimon.specs flag is added based on this line > > > >>> in aarch64- > > > >> sim.exp: > > > >> > > > >> Where does aarch64-sim.exp comes from? > > > > > > > > /usr/share/dejagnu/baseboards/aarch64-sim.exp > > > > > > > >> > > > >>> > > > >>> set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags] > > > >>> - > > > >> specs=rdimon.specs" > > > >>> > > > >> I think this is for baremetal/newlib targets, ie. aarch64-elf, not > > > >> for aarch64- linux-gnu. > > > > > > > > Yes -specs=rdimon.specs and other such flags are for use only on bare-metal > > targets. > > > > > > Hmm.. build-many-glibcs.py doesn't like either aarch64-elf or aarch64-linux- > > elf... > > > > I get a KeyError in build_compilers and build_glibcs when it tries to look up > > the config with either of those values. > > > > > > > > > > Unfortunately the build-many-glibcs.py does not have support for > > > baremetal build yet (since it is a tool created to build > > > cross-compiling toolchain using glibc). > > > > And glibc doesn't work bare-metal ...... > > > > regards > > Ramana > I guess that means that the dejagnu baseboard "aarch64-sim" is only meant to do bare-metal testing? How would one build/test GCC hosted on x86_64 and targeting aarch64 then? Is there a different simulator approach I should be using? For cross-compilers with Linux, you've got 2 options - write up a board file to use qemu in user-emulation mode or indeed system emulation mode or use real hardware and construct something using ssh / scp. R