Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 7 Apr 2018 22:14:47 -0400
From:      Alexander Kabaev <kabaev@gmail.com>
To:        Mark Millard <marklmi26-fbsd@yahoo.com>
Cc:        freebsd-toolchain@freebsd.org, John Baldwin <jhb@freebsd.org>
Subject:   Re: amd64-binutils file name structure for utils vs. for powerpc64-binutils and aarch64-binutils
Message-ID:  <20180407221447.63e016cc@kan>
In-Reply-To: <4410009D-E857-4BB0-B865-9294D24187F5@yahoo.com>
References:  <D9BAEC2B-AED4-4031-8B60-658660DBCF28@yahoo.com> <20180407184317.3ab301e2@kan> <20180407193742.1c6cd33d@kan> <4410009D-E857-4BB0-B865-9294D24187F5@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/2czACRa.oUqIcc1n9lAv4PM
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 7 Apr 2018 17:01:30 -0700
Mark Millard <marklmi26-fbsd@yahoo.com> wrote:

> On 2018-Apr-7, at 4:37 PM, Alexander Kabaev <kabaev at gmail.com>
> wrote:
>=20
> > On Sat, 7 Apr 2018 18:43:17 -0400
> > Alexander Kabaev <kabaev@gmail.com> wrote:
> >=20
> > Come to think of it, I am not sure I understand the problem.
> > amd64-binutils installs "proper" x86_64-freebsd-prefixed binaries.
> > Did you expect amd64-freebsd-* ? =20
>=20
> My understanding was that cross-build tools are now supposed
> to have the -unknown and the os version (12.0 here) even
> when the cross-build is targeting the same environment as the
> host environment. In other words: that it is not supposed to
> be the same as plain binutils for the host but as-if it was
> from a different architecture.
>=20
> But I was checking my understanding. In part because it used
> to be that, for example, on amd64 the aarch64-binutils also
> omitted the -unknown and 12.0 but now has them. I just had
> to update my environment's references to such for that. (This
> was not a self-hosted cross-build context and it changed.)
>=20
> Also, there is a recent check-in, -r466699 , for ports that,
> in part, says:
>=20
> Log:
>   Fix two more issues with r465416.
>  =20
>   - Force build of a cross-compiler by defining
> CROSS_DIRECTORY_STRUCTURE in CFLAGS even if the build host matches
> the build target.  This fixes such a cross compiler to not
> include /usr/local/lib in its default library path (e.g. amd64-gcc
> when built on amd64).
>=20
>=20
>=20
> But that was for powerpc64-gcc, not powerpc64-binutils (for example).
> I do not know for sure if similar points should also apply to
> *-binutils ports. So, again, I was checking.
>=20
> (I might have just got involved between already-made and other pending
> updates for all I know.)
>=20
>=20
> --=20
> Alexander Kabaev
>=20
> =3D=3D=3D
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)

Since I am not the maintainer of binutils ports, I missed wholesale
rename. I suspect something like the patch below will make
amd64-binutils follow the convention:

P164: https://reviews.freebsd.org/P164

--=20
Alexander Kabaev

--Sig_/2czACRa.oUqIcc1n9lAv4PM
Content-Type: application/pgp-signature
Content-Description: Цифровая подпись OpenPGP

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEExffZlZm2QeE8UVaRBxMimZJ5Ln4FAlrJexdfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM1
RjdEOTk1OTlCNjQxRTEzQzUxNTY5MTA3MTMyMjk5OTI3OTJFN0UACgkQBxMimZJ5
Ln52kg//d4dbHc7byxxoWx59iKs6qrXxvV/qRdHvuOiUfvXicMY3pR9ZvdFXCIPX
0NlUWfNvDOD3v2wMFwQ6bxp5BH8GsM0FWMDSXZ9Ve+igESg0NjM98ZL5l5bEInLB
K7THmu8WIm824bHUo/qxl5QfJy72Vqcp5z6YdTTk84rWYYztdxaRejqQAdCvHW4U
vHf8wQEN25urek4uozfcms2Y17WfYlsIcvtxXWQrrzy1XSuozo6rG3zC+nzUeStn
3vs2NUjqcwGpf/Omrb7HRHDHvKjSO8OuTf1qA3obN8AUf1rLwotYhnLxbPn3Pp+d
dDri+BrwvVQ9q9R1bdwBgqI60mBYv54EIvznUd/ILFRUtIl9s50wSNEJc/oxVFkU
XrNGThT3xDS+gx+sxCIv9mKyooiPb2TGDYpLENqYP4TJ+OcKxp6zHkXGoKWQhlWe
yiTx0SuJqCu3FJ5CuOqUDMy9X82mByeb4ER/EQKhti4DtBasBZ+uRYkLirfoPnxQ
4OmQOhySDYGv/BsfotP4ZNueeoFWUBgKSKHviNmkVGIzgJowzfeGuve/l/UFi0wg
eKAwG+JXHJ1ncLdX7NgexqSCdxZCcCtXEc2tc90Zw8O4jeryfkHxp4VIlCtX/Rxc
QaBDnI/3s+rdVv6rzjo1MsxU6lup/VXTcmrFoalh7xt9EIRILg8=
=cCRp
-----END PGP SIGNATURE-----

--Sig_/2czACRa.oUqIcc1n9lAv4PM--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180407221447.63e016cc>