On Sat, 7 Apr 2018 15:30:08 -0700 Mark Millard via freebsd-toolchain <freebsd-toolchain@freebsd.org> wrote:
> For: > > # 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 > > # 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 > > in a amd64 context . . . > > 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): > > # 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 > > The differences involve the lack of: > > -unknown > 12.0 > > (Of course, plain binutils does not have such conventions.) > > Is this expected/intended? > > > For reference: > > # 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. -- Alexander Kabaev
pgpMGummgJRFb.pgp
Description: Цифровая подпись OpenPGP
