Solved Which binutils to use on aarch64?

[Phishfry]

devel/binutils uses flavors and I am having trouble figuring out what these do:

• aarch64: aarch64-binutils
• aarch64_none_elf: aarch64-none-elf-binutils

I want to compile u-boot native on aarch64 and was researching my needed toolchain.

What is the difference with these two flavors?

 

[Phishfry]

When I look at the deleted page for the old port I get a clue.

FreshPorts -- devel/aarch64-none-elf-gcc: GNU Compiler Collection for bare metal aarch64 cross-development

GCC, the GNU Compiler Collection supporting C and C++ for arm bare metal crossbuilding.

www.freshports.org

GNU Compiler Collection for bare metal aarch64 cross-development

So is this a binutils to compile amd64 code from aarch64? An arm64 to amd64 cross compiler?

Whereas the aarch64-binutils is for native aarch64 on aarch64 compiling.

Do I have that right?

Deleted page from port before flavors this don't help.

FreshPorts -- devel/aarch64-binutils: GNU binutils for AArch64 cross-development

The GNU Binutils are a collection of binary tools. The main ones are: * ld - the GNU linker. * as - the GNU assembler. Most of these programs use BFD, the Binary File Descriptor library, to do low-level manipulation. Many of them also use the opcodes library to assemble and disassemble machine...

www.freshports.org

 

[aragats]

compile u-boot native on aarch64

For native compilation you should use native binutils, all others are for cross-compilation. In other words, on aarch64 you use its native binutils.
It doesn't matter how you compile u-boot ― it runs on bare metal anyway. E.g. I compile u-boot in FreeBSD to boot BBB into Linux.