This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
How to test aarch64 when building a cross-compiler?
- From: "Andrew Dean via gcc" <gcc at gcc dot gnu dot org>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 25 Nov 2019 19:17:02 +0000
- Subject: How to test aarch64 when building a cross-compiler?
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PgSMoiC7ZI3b8Au06y49OWXupEGQOs9zP/fSvn8gGRY=; b=cVvYIrffYA1V2JHbAgnDfJhy9jLbPhGpqnnNDO9K1Dn8IkvJoVwXqmO4vnjqoca78+Y07bcs12vWQu3dCSvDnvNQ+SJKfmesPkL5dDs64Ss/tx2ZIsaMC2VVLQASV5a/Jo7tEfYO1zAekdw/9rjezLwT5JCwZKnOGLGJvB7yZXVgoYBnALy1lrJARrZrs25jZ2XBYIRWyHCvDQ54crXlh+bQ1398rq+GDD1GzC6OijFS8H/IFCYunazRRyZwXG4B64ubEdRpkhzBWVshRZbIjND7HpVQDOKSikIAMSlBccMytLLnlHj78WhVBqqAQ3jL4390DnMPos2Ygo+nOoOckQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hcEXAYaDvSwe5lDI9svVjAcROLe3McCzMF0aMnI3ZZ9EqcQ3NbJPBS8kr3wosCzmgAGZ2arb1s1Gp6v32EMrOjENiEbTH5qlh7Hfg/qpWudmdi85EGPVVmrFmN9PYH+9YORGLgd7xHgR2eDk83bWkelK482l3iFxFyhq4zffIHpZ/6F3EgFhguFU0vSnnAcOtKgM4C782/REf1XzLKpmeIGDNLo9fUicki6vaorQnq0fOEC+9gu+xL4njjkkk3s7TB/m1va4BDdEF+8U+HRuX7UktIjYuRoABzf1zl251vfklGlW9rqku/92FMKxyram7Gw0ScI3KR+/GZpEFVysUw==
- Reply-to: Andrew Dean <Andrew dot Dean at microsoft dot com>
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:
set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags] -specs=rdimon.specs"
I've tried searching for how to address this, but so far unsuccessfully. Does anybody know what I'm missing here?
Thanks,
Andrew