Add OpenBSD target by sethjackson · Pull Request #124776 · dotnet/runtime

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

sethjackson · 2026-02-24T01:06:44Z

Was missing from the OS list.

It doesn't build quite yet but I'm hoping to land some stuff to at least get CoreCLR closer to working.

dotnet-policy-service · 2026-02-24T01:07:48Z

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

akoeplinger · 2026-02-24T09:11:46Z

I saw you opened other PRs (#124774, #124775) as well, I think it'd be good to have a tracking issue like we had for FreeBSD: #14537

/cc @jkotas

am11 · 2026-02-24T12:50:01Z

@sethjackson, the rough porting order for new OS:

create a branch in your fork like feature/openbsd-port-full (not for upstream; just accumulated miscellaneous changes)
git grep -i freebsd ":/eng' and add openbsd equivalents
git grep -i freebsd ":/src/native/minipal' and add openbsd equivalents
git grep -i freebsd ":/src/native/external' and add openbsd equivalents
git grep -i freebsd ":/src/native/libs' and add openbsd equivalents
git grep -i freebsd ":/src/coreclr/pal' and add openbsd equivalents (at this point, make sure PAL tests are passing: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/workflow/testing/coreclr/testing.md#running-pal-tests)
Then the actual coreclr port starts, but at this point, you can create feature/openbsd-port-upstream and start upstreaming meaningful chunks

Note that changes which will be made in eng/common directory needs to be upstreamed in https://github.com/dotnet/arcade repo (that automatically syncs that dir here).

Here is the guide: https://github.com/dotnet/runtime/blob/dad73abe3f99871e9dc0be8385fd0a4b0e061f64/docs/design/coreclr/botr/guide-for-porting.md (may contain some outdated/unclear bits but it gives us a good start).

jkotas · 2026-02-24T16:08:57Z

/ba-g deadletter

sethjackson · 2026-02-24T17:11:26Z

@akoeplinger more than happy to make a tracking issue to track OpenBSD support in CoreCLR. Would you like me to make that or would someone on the team need to make it? I'm happy to open it I just won't be able to and write up the details until later this week.

@am11 thanks for the porting instructions! I will be sure to follow along with this as I go.

And thanks for merging @jkotas.

akoeplinger · 2026-02-25T15:02:18Z

@sethjackson you can open the issue when you're ready, that way it's clear who is driving the effort.

sethjackson · 2026-02-26T17:51:30Z

Sounds good. Created #124911.

Add OpenBSD target
219deb2

github-actionsBot added the area-Infrastructure label Feb 24, 2026

github-project-automationBot added this to Runtime Infra Feb 24, 2026

dotnet-policy-serviceBot added the community-contribution Indicates that the PR has been added by a community member label Feb 24, 2026

build-analysisBot mentioned this pull request Feb 24, 2026
"We stopped hearing from agent Azure Pipelines 32. Verify the agent machine is running and has a healthy network connection" dotnet/dnceng#1886
Open
3 tasks

jkotas approved these changes Feb 24, 2026
View reviewed changes

jkotas merged commit a7a54a5 into dotnet:mainFeb 24, 2026
157 of 160 checks passed

github-project-automationBot moved this to Done in Runtime Infra Feb 24, 2026

sethjackson deleted the add-openbsd-target branch February 24, 2026 17:08

dotnet-maestroBot mentioned this pull request Feb 25, 2026
[main] Source code updates from dotnet/runtime dotnet/dotnet#5050
Merged

jkotas added the os-openbsd OpenBSD OS, currently not officially supported label Feb 27, 2026

am11 mentioned this pull request Feb 27, 2026
Fix pal_io.c on OpenBSD #124992
Merged

iremyux pushed a commit to iremyux/dotnet-runtime that referenced this pull request Mar 2, 2026
Add OpenBSD target (dotnet#124776)
951168a

github-actionsBot locked and limited conversation to collaborators Mar 29, 2026