Date: Tue, 31 Dec 2019 17:40:29 -0800 From: Mark Millard <marklmi@yahoo.com> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Re: A devel/freebsd-gcc*/Makefile suggestion to avoid base/binutil preventing freebsd-gcc* builds Message-ID: <252003C3-B06B-4371-A6D5-DBB3795DD0D7@yahoo.com> In-Reply-To: <8d769537-0525-f7d1-c380-4d0cfaf6a1e3@FreeBSD.org> References: <EE8FADEA-F104-4036-8056-116AE49C4BA5.ref@yahoo.com> <EE8FADEA-F104-4036-8056-116AE49C4BA5@yahoo.com> <8d769537-0525-f7d1-c380-4d0cfaf6a1e3@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Dec-31, at 16:37, John Baldwin <jhb at freebsd.org> wrote:
> On 12/26/19 7:54 PM, Mark Millard wrote:
>> Context: devel/freebsd-gcc* (for example)
>> using:
>>=20
>> --with-as=3D${LOCALBASE}/bin/${BU_PREFIX}-as \
>> --with-ld=3D${LOCALBASE}/bin/${BU_PREFIX}-ld
>>=20
>> The likes of ${BU_PREFIX}-ld possibly also
>> exists someplace else on the path in use.
>> So I suggest that the BUILD_DEPENDS and
>> RUN_DEPENDS cause the full path to be
>> checked so that the full path will be
>> created if they do not exist already.
>> So, using devel/freebsd-gcc9 as an example,
>> . . .
>>=20
>>=20
>> # svnlite diff /usr/ports/devel/freebsd-gcc9/
>> Index: /usr/ports/devel/freebsd-gcc9/Makefile
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> --- /usr/ports/devel/freebsd-gcc9/Makefile (revision 520539)
>> +++ /usr/ports/devel/freebsd-gcc9/Makefile (working copy)
>> @@ -16,8 +16,8 @@
>> LIB_DEPENDS=3D libgmp.so:math/gmp \
>> libmpfr.so:math/mpfr \
>> libmpc.so:math/mpc
>> -BUILD_DEPENDS=3D ${BU_PREFIX}-as:devel/binutils@${TARGETARCH}
>> -RUN_DEPENDS=3D ${BU_PREFIX}-as:devel/binutils@${TARGETARCH}
>> +BUILD_DEPENDS=3D =
${LOCALBASE}/bin/${BU_PREFIX}-as:devel/binutils@${TARGETARCH}
>> +RUN_DEPENDS=3D =
${LOCALBASE}/bin/${BU_PREFIX}-as:devel/binutils@${TARGETARCH}
>>=20
>> FLAVORS=3D aarch64 amd64 i386 mips mips64 powerpc powerpc64 riscv64 =
sparc64
>> TARGETARCH=3D ${FLAVOR}
>>=20
>> This avoids later not finding the file via
>> the full path in such contexts.
>=20
> I don't see why this would ever be the case that we'd have, say,
> x86_64-unknown-freebsd13.0-ld anywhere but in LOCALBASE from the
> amd64-binutils package.
>=20
> base/binutils only installs /usr/bin/ld and /usr/${BUTARGET}/bin/ld.
> It doesn't install a BUTARGET-ld binary anywhere. I might end up
> axeing /usr/BUTARGET/bin from the base/binutils package. I've
> trimmed most of the similar type files from base/gcc6 recently.
Good to know. Thanks.
(My use goes back to when base/binutils did put in place
the likes of /usr/bin/BUTARGET-ld --as reported in a
bugzilla comment back in 2018-Feb. So I'd seen the
problem in the past and had to work around it.)
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?252003C3-B06B-4371-A6D5-DBB3795DD0D7>