Date: Thu, 20 Apr 2017 07:55:48 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FYI on aarch64: building and installing devel/aarch64-gcc fails with "Unable to access file" for 6 files Message-ID: <20170420075548.66f6bc4d@kan> In-Reply-To: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net> References: <921E1189-B07D-4BFA-873B-9C2DF195D771@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/4fTKOAL_R9aJXg5g7Fir6_8
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
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 <markmi@dsl-only.net> wrote:
> The attempt to build & install devel/aarch64-gcc on a aarch64
> environment gets (I use WRKDIRPREFIX=3D/usr/obj/portswork ):
>=20
> =3D=3D=3D> Installing for aarch64-gcc-6.3.0
> =3D=3D=3D> Checking if aarch64-gcc already installed
> =3D=3D=3D> Registering installation for aarch64-gcc-6.3.0 as automatic =
=20
> 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
>=20
> Stop.
> make: stopped in /usr/ports/devel/aarch64-gcc
>=20
> =3D=3D=3D>>> Installation of aarch64-gcc-6.3.0 (devel/aarch64-gcc) failed=
=20
>=20
>=20
> 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=3D/usr/obj/portswork ):
>=20
> # more ~/aarch64-gcc_fixup.sh=20
> #!/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/aarc=
h64-unknown-freebsd12.0-gcov
>=20
> cp
> -ax /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/.build/gcc/gcov-t=
ool /usr/obj/portswork/usr/ports/devel/aarch64-gcc/work/stage/usr/local/bin=
/aarch64-unknown-freebsd12.0-gcov-tool
>=20
> 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
>=20
> 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
>=20
> 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
>=20
> 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
>=20
> That puts in place the files that are not where they are expected.
>=20
> Of course this sort of hack-then-continue would not fit well
> with poudriere use or analogous build techniques.
>=20
>=20
> The same sort of thing happens for lang/powerpc64 on a powerpc64
> environment.
>=20
> As I remember. . .
> The same sort of thing happens for lang/amd64 on a amd64
> environment.
>=20
> So I have ~/powerpc64-gcc_fixup.sh and ~/amd64-gcc_fixup.sh
> as well.
>=20
>=20
> 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).
>=20
> =3D=3D=3D
> Mark Millard
> markmi at dsl-only.net
>=20
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
--=20
Alexander Kabaev
--Sig_/4fTKOAL_R9aJXg5g7Fir6_8
Content-Type: application/pgp-signature
Content-Description: Цифровая подпись OpenPGP
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEExffZlZm2QeE8UVaRBxMimZJ5Ln4FAlj4ocRfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM1
RjdEOTk1OTlCNjQxRTEzQzUxNTY5MTA3MTMyMjk5OTI3OTJFN0UACgkQBxMimZJ5
Ln4Z1hAAqSf4Yf+BJHYKnQA4ENAWGluNnCLSBJ5NhHf4pveCOChIw7QdJKuzwNWA
jHPakWRMO8NVpWyV43zvVrFGcXIC4RWjlrCMjlAHhqOcZPcbTwsap7cnhfSWt+QO
viJH/ZNoS/zjRIv7GaYC2mgYBnpBuvlhlfK2SRoXhId6ypxr61bBTELEidyxH1kB
B3sT4W7JAtj9TlUF48tiNNDxbF8JzHPmEfRugGPtoKQZptcfN+ws5vTm26uJzII/
b720tOd6YeO+lcdX4LkmYtzd6cyFeyeubToc5TFFg0/Dp2FsBERmMSQkJEn7jrRv
MmapHrHJa2EzDn1MzlCM6NIH2oyTg3lq8bGVT/fBDC6W5tYN59voAGX15j9OKfKV
5nWiW9HoAS5U334vD540wxXysYWbMdhCFlSQLlE9bcWfqVxYCn+XsiMeWqG+k6S4
ZnC+BNKTjqwcNAbUvXvBHJX5chSL+ikyZpMMpzTSYR4SIACNopYDQAC2pYg3Ikze
DiLxz978Cr8KsvDr/BPMeVByUMJ+iBgHUtR+YA6OHZPA1n7O1fEnezG+7AC+1Yh2
FRNnb0L66MkP1IWfvakYyHx7CCPo99HSIQf7S18X2O4ICAAXsnVdgU4JJKRbL4SN
gNkapRNFGI+qNSQCBhMcfJq5kQHsQ0ftZHxIvIVvjLhR4Dny/js=
=J+po
-----END PGP SIGNATURE-----
--Sig_/4fTKOAL_R9aJXg5g7Fir6_8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170420075548.66f6bc4d>