From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 68119 invoked by alias); 25 Nov 2019 20:16:11 -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 67914 invoked by uid 89); 25 Nov 2019 20:15:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_50,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=checkout, UD:aarch64-sim.exp, aarch64simexp, hostlibraries X-HELO: mail-lj1-f172.google.com Received: from mail-lj1-f172.google.com (HELO mail-lj1-f172.google.com) (209.85.208.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Nov 2019 20:15:54 +0000 Received: by mail-lj1-f172.google.com with SMTP id j6so8415828lja.2 for ; Mon, 25 Nov 2019 12:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Rx+pl207mp2nm8LzCruklxQARPX3JI9eF5stHUlZo8=; b=ESNMdeHdynHiumoW6R+uvQuW3ewR9Zxov7in7gPX2SjtP8OMHm502ugc8Er3simr2F ZiCx8C0TIRYcCBV6X+WaLy9LbZ9cYyH5q4AshmNFTI3/krOHK4W9lDREo3v+jEPA94qs t+H6xD8vutOtMm57G6S4OZJ3CSibjT/PRJ/VC8Lehf6g6BRv21i2OY6O9OrPv1Y+wx0b Sz32D72pHmuI6GXRChzOsl31cjfFVbd88ShVF0GlCg7fBfsgOF6V7MApwXswKvp0KKw1 UYURzkQjxsU39M8hYOLHy1SqHWcmt1zh+KIoXdEy27re3uvkKGnt6kjz1sQKAKfIaO2I ybWQ== MIME-Version: 1.0 References: In-Reply-To: From: Christophe Lyon Date: Mon, 25 Nov 2019 20:16:00 -0000 Message-ID: Subject: Re: How to test aarch64 when building a cross-compiler? To: Andrew Dean Cc: "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-11/txt/msg00209.txt.bz2 On Mon, 25 Nov 2019 at 20:17, Andrew Dean via gcc wrote: > > Based on https://www.gnu.org/software/hurd/hurd/glibc.html, I'm using glibc/scripts/build-many-glibcs.py targeting aarch64-linux-gnu as so: > > build-many-glibcs.py build_dir checkout --keep all > > build-many-glibcs.py build_dir host-libraries --keep all -j 12 > > build-many-glibcs.py build_dir compilers aarch64-linux-gnu --keep all -j 12 --full-gcc > build-many-glibcs.py build_dir glibcs aarch64-linux-gnu --keep all -j 12 > > This completes successfully. However, when I then try to run the gcc tests like so: > runtest --outdir . --tool gcc --srcdir /path/to/gcc/gcc/testsuite aarch64.exp --target aarch64-linux-gnu --target_board aarch64-sim --tool_exec /path_to/build_dir/install/compilers/aarch64-linux-gnu/bin/aarch64-glibc-linux-gnu-gcc --verbose -v > > 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? > > 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. > I've tried searching for how to address this, but so far unsuccessfully. Does anybody know what I'm missing here? > > Thanks, > Andrew