Date: Fri, 22 Apr 2022 14:39:23 -0700 From: Mark Millard <marklmi@yahoo.com> To: Emmanuel Vadot <manu@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, "freebsd-arm@freebsd.org" <arm@freebsd.org> Subject: devel/aarch64-none-elf-gcc and devel/arm-none-eabi-gcc include-fixed/... handling ? Message-ID: <5E569F0E-2B53-420F-B326-0EB4CA400CBC@yahoo.com> References: <5E569F0E-2B53-420F-B326-0EB4CA400CBC.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"-" prefixed line below is as in:
/usr/ports/devel/aarch64-none-elf-gcc/Makefile
in its "post-install:" target code.
"+" prefixed below is what I expect is required to actually
have the ${RM} remove the include-fixed/... :
- ${RM} -r =
${STAGEDIR}/usr/lib/gcc/${GCC_TARGET}/${PORTVERSION}/include-fixed
+ ${RM} -r =
${STAGEDIR}${PREFIX}/lib/gcc/${GCC_TARGET}/${PORTVERSION}/include-fixed
So I expect that currently devel/aarch64-none-elf-gcc and
devel/arm-none-eabi-gcc include the include-fixed/...
material and all testing and usage has been on that basis.
Question: Which alternative below is the intent?
A) delete the ${RM} . . ./include-fixed line from the Makefile
and have the files present and used
B) fix the ${RM} . . ./include-fixed line from the Makefile
and do not have the files present (so, unused)
C) Did I mess up the interpretation somehow? (Might the path
be gcc vintage specific for some reason?)
(I've not done a general inspection of devel/*gcc so more
than I've referenced might have similar questions.)
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5E569F0E-2B53-420F-B326-0EB4CA400CBC>