Date: Sat, 7 Apr 2018 18:43:17 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Mark Millard via freebsd-toolchain <freebsd-toolchain@freebsd.org> Subject: Re: amd64-binutils file name structure for utils vs. for powerpc64-binutils and aarch64-binutils Message-ID: <20180407184317.3ab301e2@kan> In-Reply-To: <D9BAEC2B-AED4-4031-8B60-658660DBCF28@yahoo.com> References: <D9BAEC2B-AED4-4031-8B60-658660DBCF28@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/L5XJ8qET5OTur=m+KtUr=b5 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 7 Apr 2018 15:30:08 -0700 Mark Millard via freebsd-toolchain <freebsd-toolchain@freebsd.org> wrote: > For: >=20 > # pkg info "*binutils" > aarch64-binutils-2.30_2,1 > amd64-binutils-2.30_2,1 > binutils-2.30_2,1 > powerpc64-binutils-2.30_2,1 >=20 > # svnlite info /usr/ports/ | grep "Re[plv]" > Relative URL: ^/head > Repository Root: svn://svn.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 466704 > Last Changed Rev: 466704 >=20 > in a amd64 context . . . >=20 > amd64-binutils uses file naming that does not match the > patterns that aarch64-binutils and powerpc64-binutils > use. Using an example type of binutil for illustration > (in a 12.0 head context): >=20 > # find /usr/local/bin /usr/local/*freebsd* -name "*addr2line*" -print > /usr/local/bin/powerpc64-unknown-freebsd12.0-addr2line > /usr/local/bin/x86_64-freebsd-addr2line > /usr/local/bin/addr2line > /usr/local/bin/aarch64-unknown-freebsd12.0-addr2line >=20 > The differences involve the lack of: >=20 > -unknown > 12.0 >=20 > (Of course, plain binutils does not have such conventions.) >=20 > Is this expected/intended? >=20 >=20 > For reference: >=20 > # uname -apKU > FreeBSD FBSDFSSD 12.0-CURRENT FreeBSD 12.0-CURRENT r332181M amd64 > amd64 1200061 1200061 No, this is not indented, but that is how GCC/binutils configure works. When building 'native' config, it does not install full triple-prefixed binaries. I had to manually work around that in powerpc64-gcc, looks like bintuils need the same treatment.=20 --=20 Alexander Kabaev --Sig_/L5XJ8qET5OTur=m+KtUr=b5 Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEExffZlZm2QeE8UVaRBxMimZJ5Ln4FAlrJSYVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM1 RjdEOTk1OTlCNjQxRTEzQzUxNTY5MTA3MTMyMjk5OTI3OTJFN0UACgkQBxMimZJ5 Ln6a6RAAte90f16pAJwmUn6hQrhXdIQ4jZ+wpg535cSd8JO4zZahv365w0rrCciW QcwJX7/BaTF81+LiyuZwLyUnJfCbINoWyEUBtB/hHWWTMqJLWyUaxtnJDczwz/Mt 84EOvPsWS7W9PvNvfUDtCwQMKoXWYQw0aTNjnhDZCmsG1LBs8f/68kNZ+Sd4Ku3F Unjg23lbGLKBHM/D8HYhlNrFqS45zj4OtHqYh06/OeLJEKzG6hHNeRAjdR5YB4fW il9M378Eszw9/kVBf9/1Snj63pug2sPpFuWD3vqnaePCLk93P3Ojqn6s7uSfb18D qtmB16nEuSXwSvekRVsCsoaGzcN+iZrKyHE43+RGKX8fxggieWDUpg32Ifea9RKn iWGfx/zeN+1w0B25m7jibMsz3FuYSNgUPbj23uyo67t9L6Wlc0CJ9Tappq+oykAO fOCFLOxxECcLDPIvVNeECW1Ce34fhs0Xy9k9+BDs0b2UEP7Hljwnwly/xe5yfK4m RHykgjBd1lQkVWso4YB4Xx2eJyAfbBPyfM1EoHxAJZkyWr6FSwNmQ3rScf+O2kZP NtBpJH6qrfm57RXpEm61EBlGj8usO9TVeS3MskWIi8QdFp3IDsPz+1s8chOkHH7R 209uliDDWmWdybpAEpMLdLknQ3Bjlpn1dfLiE1KkK/ag1xzP6xA= =NVbo -----END PGP SIGNATURE----- --Sig_/L5XJ8qET5OTur=m+KtUr=b5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180407184317.3ab301e2>