Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump default FreeBSD version to 12.x #14069

Closed
wants to merge 1 commit into from
Closed

Conversation

ibuclaw
Copy link
Member

@ibuclaw ibuclaw commented May 3, 2022

FreeBSD 11 has been retired from the main pkg repositories (https://pkg.freebsd.org/).

@dlang-bot
Copy link
Contributor

Thanks for your pull request, @ibuclaw!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#14069"

@kinke
Copy link
Contributor

kinke commented May 3, 2022

Argh. So autotester apparently uses v11 and needs an explicit flag.

@kinke
Copy link
Contributor

kinke commented May 3, 2022

Oh and DMD v2.079 apparently doesn't work on FreeBSD 12, producing a crashing build.d executable. Maybe use GDC for the FreeBSD bootstrapping job instead?

@ljmf00
Copy link
Member

ljmf00 commented May 3, 2022

Oh and DMD v2.079 apparently doesn't work on FreeBSD 12, producing a crashing build.d executable. Maybe use GDC for the FreeBSD bootstrapping job instead?

Perhaps a problem on 12.3? We switched from 12.2 to 12.3 and only tested 12.3 when bootstrapping. Just a thought tho since it could be an old bug in the bootstrapping version.

cpu: 4
memory: 8G
timeout_in: 60m
environment:
OS_NAME: freebsd
CI_DFLAGS: -version=TARGET_FREEBSD12
CI_DFLAGS: -version=TARGET_FREEBSD13
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where are these actually used? I grepped for TARGET_FREEBSD in dmd/druntime/Phobos, no relevant hits.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I belive its just for future convenience, but yeah, probably worth to be on the build system itself rather than the CI config

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently someone removed the code that used this version condition.

Copy link
Member Author

@ibuclaw ibuclaw May 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably also means that the current 12.x pipeline is likely a sham, as the built compiler would be default targetting FreeBSD 11 if this is ignored.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh yeah probably. - This probably fell under the carpet with -target=… cross-compilation support. CI_DFLAGS are most likely not sufficient in that case (only affecting dmd/druntime/Phobos builds, not the default target of the built DMD).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's correct. git log --pickaxe-regex tells me ee446a0 from #12508 .

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cross referencing #14071

@ljmf00 ljmf00 added the Blocking Other Work review and pulling should be a priority label May 3, 2022
@ibuclaw
Copy link
Member Author

ibuclaw commented May 5, 2022

We'll bump the image post-release.

As the auto-tester is still using FreeBSD 11, it's not going to work to bump the default in dmd's code. Better off reviving the TARGET_FREEBSD version and using that in the Cirrus-CI pipelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocking Other Work review and pulling should be a priority Continuous Integration
Projects
None yet
4 participants