Xen does not currently document how to build the hypervisor on macOS, and
there is no Darwin configuration for selecting a Homebrew-based GNU
toolchain. Native builds are not supported; the hypervisor must be
cross-built with a GNU toolchain and GNU make/sed.

Add a minimal Darwin.mk which selects the GNU tool definitions used by
the macOS workflow and point to the build guide for required tools and
setup. Document the Homebrew cross toolchain and GNU tools needed to
build the hypervisor on macOS.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
---
 config/Darwin.mk            |  6 ++++
 docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
 2 files changed, 72 insertions(+)
 create mode 100644 config/Darwin.mk
 create mode 100644 docs/misc/build-on-macos.md

diff --git a/config/Darwin.mk b/config/Darwin.mk
new file mode 100644
index 000000000000..a4e3efa81842
--- /dev/null
+++ b/config/Darwin.mk
@@ -0,0 +1,6 @@
+# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
+# See docs/misc/build-on-macos.md for required tools and setup.
+include $(XEN_ROOT)/config/StdGNU.mk
+
+# We are always cross compiling so fake COMPILE_ARCH
+XEN_COMPILE_ARCH = Darwin
diff --git a/docs/misc/build-on-macos.md b/docs/misc/build-on-macos.md
new file mode 100644
index 000000000000..6b56cd8eccab
--- /dev/null
+++ b/docs/misc/build-on-macos.md
@@ -0,0 +1,66 @@
+# Building Xen Hypervisor on macOS
+
+This guide explains how to cross-compile the Xen hypervisor (xen
+subdirectory only) on macOS. This does **not** build the tools.
+
+## Prerequisites
+
+Install the following packages using Homebrew:
+
+```bash
+# Cross-compilation toolchain for ARM64
+brew install aarch64-elf-gcc
+
+# GNU tools (required for compatibility)
+brew install make gnu-sed
+```
+
+Homebrew installs under `/opt/homebrew` on Apple Silicon and `/usr/local` on
+Intel Macs. Adjust paths below accordingly.
+
+### Verification
+
+Verify your installation:
+
+```bash
+# Check cross compiler
+aarch64-elf-gcc --version
+
+# Check GNU make (adjust prefix if needed)
+/opt/homebrew/opt/make/libexec/gnubin/make --version
+
+# Check GNU sed (adjust prefix if needed)
+/opt/homebrew/opt/gnu-sed/libexec/gnubin/sed --version
+```
+
+## Building the Hypervisor
+
+Set up GNU tools in PATH and build:
+
+```bash
+# Set up GNU tools in PATH (adjust prefix if needed)
+export PATH="/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/make/libexec/gnubin:$PATH"
+
+# Build Xen hypervisor only (in-tree)
+cd xen/
+make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc
+
+# Optional: out-of-tree build directory
+# make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc O=$PWD/build-mac
+```
+
+## Architecture Support
+
+Currently supported architectures:
+
+- **ARM64** (`arm64`) - Default, uses `aarch64-elf-gcc`
+
+Other targets may work if the corresponding cross toolchain is installed,
+but this guide has only been tested on ARM64.
+
+## Limitations
+
+- **Hypervisor only**: This only builds the Xen hypervisor, not the tools
+- **Cross-compilation only**: Native builds are not supported
+- **macOS-specific**: Instructions optimized for macOS with Homebrew
+- **GNU tools required**: Native BSD tools are not compatible
-- 
2.52.0

On Thu, Feb 05, 2026 at 12:33:54PM +0100, Bertrand Marquis wrote:
> Xen does not currently document how to build the hypervisor on macOS, and
> there is no Darwin configuration for selecting a Homebrew-based GNU
> toolchain. Native builds are not supported; the hypervisor must be
> cross-built with a GNU toolchain and GNU make/sed.
> 
> Add a minimal Darwin.mk which selects the GNU tool definitions used by
> the macOS workflow and point to the build guide for required tools and
> setup. Document the Homebrew cross toolchain and GNU tools needed to
> build the hypervisor on macOS.
> 
> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
> ---
>  config/Darwin.mk            |  6 ++++
>  docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>  2 files changed, 72 insertions(+)
>  create mode 100644 config/Darwin.mk
>  create mode 100644 docs/misc/build-on-macos.md
> 
> diff --git a/config/Darwin.mk b/config/Darwin.mk
> new file mode 100644
> index 000000000000..a4e3efa81842
> --- /dev/null
> +++ b/config/Darwin.mk
> @@ -0,0 +1,6 @@
> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
> +# See docs/misc/build-on-macos.md for required tools and setup.
> +include $(XEN_ROOT)/config/StdGNU.mk
> +
> +# We are always cross compiling so fake COMPILE_ARCH
> +XEN_COMPILE_ARCH = Darwin
> diff --git a/docs/misc/build-on-macos.md b/docs/misc/build-on-macos.md
> new file mode 100644
> index 000000000000..6b56cd8eccab
> --- /dev/null
> +++ b/docs/misc/build-on-macos.md
> @@ -0,0 +1,66 @@
> +# Building Xen Hypervisor on macOS
> +
> +This guide explains how to cross-compile the Xen hypervisor (xen
> +subdirectory only) on macOS. This does **not** build the tools.

More on this below, I'm not sure I would call it a "cross-compile".
Only when doing so from a x86 silicon Mac?

> +## Prerequisites
> +
> +Install the following packages using Homebrew:
> +
> +```bash
> +# Cross-compilation toolchain for ARM64
> +brew install aarch64-elf-gcc
> +
> +# GNU tools (required for compatibility)
> +brew install make gnu-sed
> +```

Installing make / sed are not strictly needed.

> +
> +Homebrew installs under `/opt/homebrew` on Apple Silicon and `/usr/local` on
> +Intel Macs. Adjust paths below accordingly.
> +
> +### Verification
> +
> +Verify your installation:
> +
> +```bash
> +# Check cross compiler
> +aarch64-elf-gcc --version
> +
> +# Check GNU make (adjust prefix if needed)
> +/opt/homebrew/opt/make/libexec/gnubin/make --version
> +
> +# Check GNU sed (adjust prefix if needed)
> +/opt/homebrew/opt/gnu-sed/libexec/gnubin/sed --version
> +```

Checking for make / sed can be removed.

> +
> +## Building the Hypervisor
> +
> +Set up GNU tools in PATH and build:
> +
> +```bash
> +# Set up GNU tools in PATH (adjust prefix if needed)
> +export PATH="/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/make/libexec/gnubin:$PATH"

Do you really need the gnubin?  I think this was only for sed / make,
which is not really needed.

> +
> +# Build Xen hypervisor only (in-tree)
> +cd xen/
> +make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc
> +
> +# Optional: out-of-tree build directory
> +# make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc O=$PWD/build-mac
> +```
> +
> +## Architecture Support
> +
> +Currently supported architectures:
> +
> +- **ARM64** (`arm64`) - Default, uses `aarch64-elf-gcc`

It could possibly also use the llvm package from homebrew, but I can
add later if I get some time to test.

> +
> +Other targets may work if the corresponding cross toolchain is installed,
> +but this guide has only been tested on ARM64.
> +
> +## Limitations
> +
> +- **Hypervisor only**: This only builds the Xen hypervisor, not the tools
> +- **Cross-compilation only**: Native builds are not supported

Probably a more philosophical question, but is it really a cross
compilation if I'm building an arm64 Xen on Apple arm64 silicon?

Sure, it might use a different toolchain from native, but it's still a
"native" build from an architectural perspective?

> +- **macOS-specific**: Instructions optimized for macOS with Homebrew
> +- **GNU tools required**: Native BSD tools are not compatible

That last item can be removed.

Thanks, Roger.

Hi Roger,

> On 5 Feb 2026, at 18:07, Roger Pau Monné <roger.pau@citrix.com> wrote:
> 
> On Thu, Feb 05, 2026 at 12:33:54PM +0100, Bertrand Marquis wrote:
>> Xen does not currently document how to build the hypervisor on macOS, and
>> there is no Darwin configuration for selecting a Homebrew-based GNU
>> toolchain. Native builds are not supported; the hypervisor must be
>> cross-built with a GNU toolchain and GNU make/sed.
>> 
>> Add a minimal Darwin.mk which selects the GNU tool definitions used by
>> the macOS workflow and point to the build guide for required tools and
>> setup. Document the Homebrew cross toolchain and GNU tools needed to
>> build the hypervisor on macOS.
>> 
>> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
>> ---
>> config/Darwin.mk            |  6 ++++
>> docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>> 2 files changed, 72 insertions(+)
>> create mode 100644 config/Darwin.mk
>> create mode 100644 docs/misc/build-on-macos.md
>> 
>> diff --git a/config/Darwin.mk b/config/Darwin.mk
>> new file mode 100644
>> index 000000000000..a4e3efa81842
>> --- /dev/null
>> +++ b/config/Darwin.mk
>> @@ -0,0 +1,6 @@
>> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
>> +# See docs/misc/build-on-macos.md for required tools and setup.
>> +include $(XEN_ROOT)/config/StdGNU.mk
>> +
>> +# We are always cross compiling so fake COMPILE_ARCH
>> +XEN_COMPILE_ARCH = Darwin
>> diff --git a/docs/misc/build-on-macos.md b/docs/misc/build-on-macos.md
>> new file mode 100644
>> index 000000000000..6b56cd8eccab
>> --- /dev/null
>> +++ b/docs/misc/build-on-macos.md
>> @@ -0,0 +1,66 @@
>> +# Building Xen Hypervisor on macOS
>> +
>> +This guide explains how to cross-compile the Xen hypervisor (xen
>> +subdirectory only) on macOS. This does **not** build the tools.
> 
> More on this below, I'm not sure I would call it a "cross-compile".
> Only when doing so from a x86 silicon Mac?

As Jan mentioned we are not building on Linux so it can be considered
cross compiling.

> 
>> +## Prerequisites
>> +
>> +Install the following packages using Homebrew:
>> +
>> +```bash
>> +# Cross-compilation toolchain for ARM64
>> +brew install aarch64-elf-gcc
>> +
>> +# GNU tools (required for compatibility)
>> +brew install make gnu-sed
>> +```
> 
> Installing make / sed are not strictly needed.

Ack

> 
>> +
>> +Homebrew installs under `/opt/homebrew` on Apple Silicon and `/usr/local` on
>> +Intel Macs. Adjust paths below accordingly.
>> +
>> +### Verification
>> +
>> +Verify your installation:
>> +
>> +```bash
>> +# Check cross compiler
>> +aarch64-elf-gcc --version
>> +
>> +# Check GNU make (adjust prefix if needed)
>> +/opt/homebrew/opt/make/libexec/gnubin/make --version
>> +
>> +# Check GNU sed (adjust prefix if needed)
>> +/opt/homebrew/opt/gnu-sed/libexec/gnubin/sed --version
>> +```
> 
> Checking for make / sed can be removed.

Ack

> 
>> +
>> +## Building the Hypervisor
>> +
>> +Set up GNU tools in PATH and build:
>> +
>> +```bash
>> +# Set up GNU tools in PATH (adjust prefix if needed)
>> +export PATH="/opt/homebrew/opt/gnu-sed/libexec/gnubin:/opt/homebrew/opt/make/libexec/gnubin:$PATH"
> 
> Do you really need the gnubin?  I think this was only for sed / make,
> which is not really needed.

I do not need anything anymore, just the compiler ...

> 
>> +
>> +# Build Xen hypervisor only (in-tree)
>> +cd xen/
>> +make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc
>> +
>> +# Optional: out-of-tree build directory
>> +# make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-elf- HOSTCC=gcc O=$PWD/build-mac
>> +```
>> +
>> +## Architecture Support
>> +
>> +Currently supported architectures:
>> +
>> +- **ARM64** (`arm64`) - Default, uses `aarch64-elf-gcc`
> 
> It could possibly also use the llvm package from homebrew, but I can
> add later if I get some time to test.

yes ..

> 
>> +
>> +Other targets may work if the corresponding cross toolchain is installed,
>> +but this guide has only been tested on ARM64.
>> +
>> +## Limitations
>> +
>> +- **Hypervisor only**: This only builds the Xen hypervisor, not the tools
>> +- **Cross-compilation only**: Native builds are not supported
> 
> Probably a more philosophical question, but is it really a cross
> compilation if I'm building an arm64 Xen on Apple arm64 silicon?
> 
> Sure, it might use a different toolchain from native, but it's still a
> "native" build from an architectural perspective?
> 
>> +- **macOS-specific**: Instructions optimized for macOS with Homebrew
>> +- **GNU tools required**: Native BSD tools are not compatible
> 
> That last item can be removed.

At the end almost everything can be removed, the only "mac os" specific
instruction would be to install gcc through homebrew but there are other
solutions (cross-tools, llvm, downloading a pre compiled gcc, compiling
it yourself, ....you name it) so what would only remain here would be
instructions on how to compile the hypervisor which is not mac os specific.

So i will remove that file and just push a small patch adding Darwin.mk
with an updated comment.

Cheers
Bertrand

> 
> Thanks, Roger.

On 05.02.2026 18:07, Roger Pau Monné wrote:
> On Thu, Feb 05, 2026 at 12:33:54PM +0100, Bertrand Marquis wrote:
>> +## Limitations
>> +
>> +- **Hypervisor only**: This only builds the Xen hypervisor, not the tools
>> +- **Cross-compilation only**: Native builds are not supported
> 
> Probably a more philosophical question, but is it really a cross
> compilation if I'm building an arm64 Xen on Apple arm64 silicon?
> 
> Sure, it might use a different toolchain from native, but it's still a
> "native" build from an architectural perspective?

"Cross" aiui covers both OS (i.e. ABI) and hardware. Building x86 Linux
binaries on e.g. Windows is "cross", too. (Strictly speaking it's the
target triplet that is commonly used in at least GNU - if any part
differs, it's "cross". It just so happens that Xen uses Linux'es ABI,
and hence its building is native on identical-arch Linux.)

Jan

> On 6 Feb 2026, at 07:22, Jan Beulich <jbeulich@suse.com> wrote:
> 
> On 05.02.2026 18:07, Roger Pau Monné wrote:
>> On Thu, Feb 05, 2026 at 12:33:54PM +0100, Bertrand Marquis wrote:
>>> +## Limitations
>>> +
>>> +- **Hypervisor only**: This only builds the Xen hypervisor, not the tools
>>> +- **Cross-compilation only**: Native builds are not supported
>> 
>> Probably a more philosophical question, but is it really a cross
>> compilation if I'm building an arm64 Xen on Apple arm64 silicon?
>> 
>> Sure, it might use a different toolchain from native, but it's still a
>> "native" build from an architectural perspective?
> 
> "Cross" aiui covers both OS (i.e. ABI) and hardware. Building x86 Linux
> binaries on e.g. Windows is "cross", too. (Strictly speaking it's the
> target triplet that is commonly used in at least GNU - if any part
> differs, it's "cross". It just so happens that Xen uses Linux'es ABI,
> and hence its building is native on identical-arch Linux.)

Agree, i will put a small comment on top of the line in darwin.mk
spelling it out:

Xen uses Linux'es ABI so we are cross compiling on Mac OS. 
Force COMPILE_ARCH to a fake value to make sure it is always the case. 

Bertrand

> 
> Jan

On 05.02.2026 12:33, Bertrand Marquis wrote:
> Xen does not currently document how to build the hypervisor on macOS, and
> there is no Darwin configuration for selecting a Homebrew-based GNU
> toolchain. Native builds are not supported; the hypervisor must be
> cross-built with a GNU toolchain and GNU make/sed.
> 
> Add a minimal Darwin.mk which selects the GNU tool definitions used by
> the macOS workflow and point to the build guide for required tools and
> setup. Document the Homebrew cross toolchain and GNU tools needed to
> build the hypervisor on macOS.
> 
> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
> ---
>  config/Darwin.mk            |  6 ++++
>  docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>  2 files changed, 72 insertions(+)
>  create mode 100644 config/Darwin.mk
>  create mode 100644 docs/misc/build-on-macos.md

I'm sorry, I should have paid attention already on the RFC, but: With all
other Pandoc files in this directory being named *.pandoc, do we really want
to have an outlier named *.md there?

> --- /dev/null
> +++ b/config/Darwin.mk
> @@ -0,0 +1,6 @@
> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
> +# See docs/misc/build-on-macos.md for required tools and setup.
> +include $(XEN_ROOT)/config/StdGNU.mk

Given Roger's consideration towards possibly using a more MacOS-native
build arrangement as an alternative, I'm actually not quite sure this should
then be the default mode here. Roger, what are your thoughts?

Jan

Hi,

With Roger's patch removing the need for GNU sed, it appears that
compilation is also working with Mac OS make.

> On 5 Feb 2026, at 13:29, Jan Beulich <jbeulich@suse.com> wrote:
> 
> On 05.02.2026 12:33, Bertrand Marquis wrote:
>> Xen does not currently document how to build the hypervisor on macOS, and
>> there is no Darwin configuration for selecting a Homebrew-based GNU
>> toolchain. Native builds are not supported; the hypervisor must be
>> cross-built with a GNU toolchain and GNU make/sed.
>> 
>> Add a minimal Darwin.mk which selects the GNU tool definitions used by
>> the macOS workflow and point to the build guide for required tools and
>> setup. Document the Homebrew cross toolchain and GNU tools needed to
>> build the hypervisor on macOS.
>> 
>> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
>> ---
>> config/Darwin.mk            |  6 ++++
>> docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>> 2 files changed, 72 insertions(+)
>> create mode 100644 config/Darwin.mk
>> create mode 100644 docs/misc/build-on-macos.md
> 
> I'm sorry, I should have paid attention already on the RFC, but: With all
> other Pandoc files in this directory being named *.pandoc, do we really want
> to have an outlier named *.md there?

Right but this might not be needed anymore as the only thing needed after Roger's
patch is only a toolchain so brew is one solution but there are a lot of others.

> 
>> --- /dev/null
>> +++ b/config/Darwin.mk
>> @@ -0,0 +1,6 @@
>> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
>> +# See docs/misc/build-on-macos.md for required tools and setup.
>> +include $(XEN_ROOT)/config/StdGNU.mk
> 
> Given Roger's consideration towards possibly using a more MacOS-native
> build arrangement as an alternative, I'm actually not quite sure this should
> then be the default mode here. Roger, what are your thoughts?

Even with Mac OS sed and make working, something is still needed here to 
compile on Mac OS.

What would you suggest the default mode should be here ? Mac OS is not GNU
but everything used correspond to what is defined by StdGNU.mk.

I am only forcing cross compilation here to prevent using the host toolchain.

What do you think i should put there instead ?

I have been keeping that downstream for a while, it is kind of sad that people cannot
compile on mac os just because of this file missing.

Cheers
Bertrand

> 
> Jan

On 05.02.2026 16:30, Bertrand Marquis wrote:
>> On 5 Feb 2026, at 13:29, Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 05.02.2026 12:33, Bertrand Marquis wrote:
>>> Xen does not currently document how to build the hypervisor on macOS, and
>>> there is no Darwin configuration for selecting a Homebrew-based GNU
>>> toolchain. Native builds are not supported; the hypervisor must be
>>> cross-built with a GNU toolchain and GNU make/sed.
>>>
>>> Add a minimal Darwin.mk which selects the GNU tool definitions used by
>>> the macOS workflow and point to the build guide for required tools and
>>> setup. Document the Homebrew cross toolchain and GNU tools needed to
>>> build the hypervisor on macOS.
>>>
>>> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
>>> ---
>>> config/Darwin.mk            |  6 ++++
>>> docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>>> 2 files changed, 72 insertions(+)
>>> create mode 100644 config/Darwin.mk
>>> create mode 100644 docs/misc/build-on-macos.md
>>
>> I'm sorry, I should have paid attention already on the RFC, but: With all
>> other Pandoc files in this directory being named *.pandoc, do we really want
>> to have an outlier named *.md there?
> 
> Right but this might not be needed anymore as the only thing needed after Roger's
> patch is only a toolchain so brew is one solution but there are a lot of others.

Even better.

>>> --- /dev/null
>>> +++ b/config/Darwin.mk
>>> @@ -0,0 +1,6 @@
>>> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
>>> +# See docs/misc/build-on-macos.md for required tools and setup.
>>> +include $(XEN_ROOT)/config/StdGNU.mk
>>
>> Given Roger's consideration towards possibly using a more MacOS-native
>> build arrangement as an alternative, I'm actually not quite sure this should
>> then be the default mode here. Roger, what are your thoughts?
> 
> Even with Mac OS sed and make working, something is still needed here to 
> compile on Mac OS.
> 
> What would you suggest the default mode should be here ? Mac OS is not GNU
> but everything used correspond to what is defined by StdGNU.mk.
> 
> I am only forcing cross compilation here to prevent using the host toolchain.

That part is okay with me.

> What do you think i should put there instead ?

Using StdGNU.mk may still be okay, as long as the comment properly represents
the overall situation.

Jan

Hi Jan,

> On 5 Feb 2026, at 16:43, Jan Beulich <jbeulich@suse.com> wrote:
> 
> On 05.02.2026 16:30, Bertrand Marquis wrote:
>>> On 5 Feb 2026, at 13:29, Jan Beulich <jbeulich@suse.com> wrote:
>>> 
>>> On 05.02.2026 12:33, Bertrand Marquis wrote:
>>>> Xen does not currently document how to build the hypervisor on macOS, and
>>>> there is no Darwin configuration for selecting a Homebrew-based GNU
>>>> toolchain. Native builds are not supported; the hypervisor must be
>>>> cross-built with a GNU toolchain and GNU make/sed.
>>>> 
>>>> Add a minimal Darwin.mk which selects the GNU tool definitions used by
>>>> the macOS workflow and point to the build guide for required tools and
>>>> setup. Document the Homebrew cross toolchain and GNU tools needed to
>>>> build the hypervisor on macOS.
>>>> 
>>>> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
>>>> ---
>>>> config/Darwin.mk            |  6 ++++
>>>> docs/misc/build-on-macos.md | 66 +++++++++++++++++++++++++++++++++++++
>>>> 2 files changed, 72 insertions(+)
>>>> create mode 100644 config/Darwin.mk
>>>> create mode 100644 docs/misc/build-on-macos.md
>>> 
>>> I'm sorry, I should have paid attention already on the RFC, but: With all
>>> other Pandoc files in this directory being named *.pandoc, do we really want
>>> to have an outlier named *.md there?
>> 
>> Right but this might not be needed anymore as the only thing needed after Roger's
>> patch is only a toolchain so brew is one solution but there are a lot of others.
> 
> Even better.
> 
>>>> --- /dev/null
>>>> +++ b/config/Darwin.mk
>>>> @@ -0,0 +1,6 @@
>>>> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
>>>> +# See docs/misc/build-on-macos.md for required tools and setup.
>>>> +include $(XEN_ROOT)/config/StdGNU.mk
>>> 
>>> Given Roger's consideration towards possibly using a more MacOS-native
>>> build arrangement as an alternative, I'm actually not quite sure this should
>>> then be the default mode here. Roger, what are your thoughts?
>> 
>> Even with Mac OS sed and make working, something is still needed here to 
>> compile on Mac OS.
>> 
>> What would you suggest the default mode should be here ? Mac OS is not GNU
>> but everything used correspond to what is defined by StdGNU.mk.
>> 
>> I am only forcing cross compilation here to prevent using the host toolchain.
> 
> That part is okay with me.
> 
>> What do you think i should put there instead ?
> 
> Using StdGNU.mk may still be okay, as long as the comment properly represents
> the overall situation.

Agree.

What do you think of the following:

Use GNU tool definitions as the tools we are using are either GNU compatible
or we only use features which are supported on Mac OS.

Bertrand

On 05.02.2026 16:58, Bertrand Marquis wrote:
>> On 5 Feb 2026, at 16:43, Jan Beulich <jbeulich@suse.com> wrote:
>> On 05.02.2026 16:30, Bertrand Marquis wrote:
>>>> On 5 Feb 2026, at 13:29, Jan Beulich <jbeulich@suse.com> wrote:
>>>> On 05.02.2026 12:33, Bertrand Marquis wrote:
>>>>> --- /dev/null
>>>>> +++ b/config/Darwin.mk
>>>>> @@ -0,0 +1,6 @@
>>>>> +# Use GNU tool definitions; the macOS workflow relies on Homebrew GNU tools.
>>>>> +# See docs/misc/build-on-macos.md for required tools and setup.
>>>>> +include $(XEN_ROOT)/config/StdGNU.mk
>>>>
>>>> Given Roger's consideration towards possibly using a more MacOS-native
>>>> build arrangement as an alternative, I'm actually not quite sure this should
>>>> then be the default mode here. Roger, what are your thoughts?
>>>
>>> Even with Mac OS sed and make working, something is still needed here to 
>>> compile on Mac OS.
>>>
>>> What would you suggest the default mode should be here ? Mac OS is not GNU
>>> but everything used correspond to what is defined by StdGNU.mk.
>>>
>>> I am only forcing cross compilation here to prevent using the host toolchain.
>>
>> That part is okay with me.
>>
>>> What do you think i should put there instead ?
>>
>> Using StdGNU.mk may still be okay, as long as the comment properly represents
>> the overall situation.
> 
> Agree.
> 
> What do you think of the following:
> 
> Use GNU tool definitions as the tools we are using are either GNU compatible
> or we only use features which are supported on Mac OS.

Sounds good.

Jan