Many thanks, Jim, for the detailed reply. You hit the nail on the top. I will try if I can gain some decision help from it.
-- Christoph > Am 22.07.2025 um 12:15 schrieb Jim DeLaHunt <[email protected]>: > > Hello, Christoph: > > On 2025-07-22 00:48, Christoph Kukulies via macports-users wrote: >> I'm in the situation - maybe there is a solution using macports - that I >> need the >> | Toolchain [*] >> | >> | >> ---------------------------------------------------------------------------------- >> | >> | Build | Host | Target >> | >> | >> ---------------------------------------------------------------------------------- >> | > ...[detail left out]... > >> | macOS (x86_64) | macOS (x86_64) | aarch64-none-elf >> | >> | macOS (x86_64) | macOS (x86_64) | arm-none-eabi >> <<<<<<<<<<<<< |<<<<*** >> | macOS (Apple silicon) | macOS (Apple silicon) | aarch64-none-elf >> | > ...[detail left out]... >> | >> ---------------------------------------------------------------------------------- >> | >> toolchain. > > I'm not entirely sure I understand what you are asking. Let me see if I can > figure it out. > > You include this big table, but from the "<<<" arrow, I think you are asking, > how do I build the "gnu-devtools-for-arm" project for just the one > combination of: > > Build: macOS (x86_64), Host: macOS (x86_64), Target: arm-none-eabi > > And, > >> As of https://gitlab.arm.com/tooling/gnu-devtools-for-arm/-/blob/main/ >> README.md homebrew is heavily involved. >> What choices are there? > > You see that the "gnu-devtools-for-arm" project supplies build instructions, > which require you to gather a lot of tools, from autoconf to zlib1g-dev. But > the macOS part of the instructions only say how to gather those tools using > homebrew. > > I think you are asking, can I gather those tools using MacPorts? If so, how? > > If I understand you correctly, then I think the answer is: Maybe, probably, > but you will have to figure out how. Maybe there will be some obstacles > which you have to figure out. > > You are in the same situation as the person who wrote those instructions for > macOS. Except they had to figure out how to gather the tools using homebrew, > and you have to figure out how to gather the tools musing MacPorts. > > I would suggest you go through the list of homebrew recipes in the > instructions. See which tools each of those recipes installs. Find out which > port in MacPorts installs the same tool. Install that port from MacPorts. > > When you have installed all the tools, try to do the build. If it works, > great. If it doesn't work, then you have a puzzle to solve. > > Does that help? > > Best regards, > --Jim DeLaHunt >
signature.asc
Description: Message signed with OpenPGP
