aarch64-gcc is not a full compiler, but one intended to be used as cross toolchain. Said that, when built on x86-64, it does have gcov and man pages, so this must be an artefact of your build environment or your aarch64 setup, as this never was tested when run natively nor was it meant to be - there is unfinished work in ports/base to create native toolchain.
Please provide full log of your port build soemwhere, though I will not
be able to look at it under weekend at the earliest.
% pkg info -l aarch64-gcc-6.3.0 | grep gcov
/usr/local/bin/aarch64-unknown-freebsd12.0-gcov
/usr/local/bin/aarch64-unknown-freebsd12.0-gcov-tool
/usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include/gcov-counter.def
/usr/local/lib/gcc/aarch64-unknown-freebsd12.0/6.3.0/plugin/include/gcov-io.h
/usr/local/man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz
Thanks,
On Wed, 19 Apr 2017 17:09:34 -0700
Mark Millard <mar...@dsl-only.net> wrote:
> The attempt to build & install devel/aarch64-gcc on a aarch64
> environment gets (I use WRKDIRPREFIX=/usr/obj/portswork ):
>
> ===> Installing for aarch64-gcc-6.3.0
> ===> Checking if aarch64-gcc already installed
> ===> Registering installation for aarch64-gcc-6.3.0 as automatic
> pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aarch64-unknown-freebsd12.0-gcov:No
> such file or directory pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aarch64-unknown-freebsd12.0-gcov-tool:No
> such file or directory pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-cpp.1.gz:No
> such file or directory pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-g++.1.gz:No
> such file or directory pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-gcc.1.gz:No
> such file or directory pkg-static: Unable to access
> file
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz:No
> such file or directory *** Error code 74
>
> Stop.
> make: stopped in /usr/ports/devel/aarch64-gcc
>
> ===>>> Installation of aarch64-gcc-6.3.0 (devel/aarch64-gcc) failed
>
>
> A hack before doing a portmaster -CDK lang/aarch64-gcc to continue
> the build/install is to execute the script shown below (I use
> WRKDIRPREFIX=/usr/obj/portswork ):
>
> # more ~/aarch64-gcc_fixup.sh
> #!/bin/sh
> cp
> -ax /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aarch64-unknown-freebsd12.0-gcov
>
> cp
> -ax /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov-tool
> /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin/aarch64-unknown-freebsd12.0-gcov-tool
>
> gzip
> -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/cpp.1
> > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-cpp.1.gz
>
> gzip
> -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/g++.1
> > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-g++.1.gz
>
> gzip
> -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/doc/gcc.1
> > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-gcc.1.gz
>
> gzip
> -c /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/gcc-*/gcc/doc/gcov.1
> > /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/man/man1/aarch64-unknown-freebsd12.0-gcov.1.gz
>
> That puts in place the files that are not where they are expected.
>
> Of course this sort of hack-then-continue would not fit well
> with poudriere use or analogous build techniques.
>
>
> The same sort of thing happens for lang/powerpc64 on a powerpc64
> environment.
>
> As I remember. . .
> The same sort of thing happens for lang/amd64 on a amd64
> environment.
>
> So I have ~/powerpc64-gcc_fixup.sh and ~/amd64-gcc_fixup.sh
> as well.
>
>
> I get to these ???-gcc's by trying to install a
> self-hosted lang/???-xtoolchain-gcc in each case.
> Such allows for experimenting with self-hosted gcc
> based system builds that are libc++ based (instead
> of using gcc 4.2.1).
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> _______________________________________________
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
--
Alexander Kabaev
pgpBs3WB8qnxL.pgp
Description: Цифровая подпись OpenPGP
