use older os to compiler so dynamic libraries work better

[mateoconlechuga]

See relevant toolchain issue here: CE-Programming/toolchain#439

[adriweb]

Hmm can jacobly launch CI on this or something, to see if it builds as expected?

[mateoconlechuga]

Hmm can jacobly launch CI on this or something, to see if it builds as expected?

It already built fine on my fork: https://github.com/mateoconlechuga/llvm-project/actions/runs/5039720221/jobs/9038047940

[adriweb]

Ah great, merge time then 👀

[mateoconlechuga]

waits 3 weeks for the merge

[mateoconlechuga]

Bump bump 😃

[mateoconlechuga]

I'm going to fork the project at this point :(

[adriweb]

Ok so I propose some modifications to just add the older OSes instead, since @jacobly0 said this (IRC).

06:06:40 <@jacobly> I have no problem with adding build configurations, but I'm not removing the existing ones

I guess now they have to be accepted so the PR gets updated, then jacobly can merge it.

[adriweb]

Suggested change

	runs-on: [ubuntu-20.04, macos-11, windows-latest]
	runs-on: [ubuntu-20.04, ubuntu-latest, macos-11, macos-latest, windows-latest]

[adriweb]

Suggested change

	runs-on: [ubuntu-20.04, macos-11, windows-latest]
	runs-on: [ubuntu-20.04, ubuntu-latest, macos-11, macos-latest, windows-latest]

[adriweb]

Suggested change

	runs-on: [ubuntu-20.04, macos-11, windows-latest]
	runs-on: [ubuntu-20.04, ubuntu-latest, macos-11, macos-latest, windows-latest]

[adriweb]

Suggested change

	runs-on: [ubuntu-20.04, macos-11, windows-latest]
	runs-on: [ubuntu-20.04, ubuntu-latest, macos-11, macos-latest, windows-latest]

[adriweb]

Suggested change

	runs-on: [ubuntu-20.04, macos-11, windows-latest]
	runs-on: [ubuntu-20.04, ubuntu-latest, macos-11, macos-latest, windows-latest]

[adriweb]

Well in addition to that now, I suppose we have to use ${{matrix.runs-on}} instead of ${{runner.os}} in the various named resources, all good with that?

[adriweb]

Easier solution, regarding my last comment, no need to change the names, we can just upload the binaries if the currently running VM is the version we want. The other (newer) VMs will just continue to be there to test the build, that's fine.

(23:32:18 <@jacobly> I don't care about the artifact names, feel free to change the backwards compatible names to now be the old versions)

[adriweb]

Well I put all the names differently for now, jacobly is able to merge it if it's ok https://github.com/adriweb/llvm-project/actions/runs/5335820947
Then we just have to make the toolchain use those names when downloading files in its CI.

[mateoconlechuga]

I'm going to fork this into CE-Programming since the PR doesn't seem to want to be merged :(

[adriweb]

Well he said he'll do it so :P
(but when?)

Also take the commit from my fork I guess, if you really want to do that.

[mateoconlechuga]

I guess I can wait a bit longer :)

[adriweb]

So, I did the thing to upload selected artifacts to a "nightly" pre-release like in CEmu or the toolchain, it works fine, as we can see in the release files :)
So if this is merged too, there won't be a need to depend on jacobly's server script to fetch artifacts, but most importantly, we don't have the 90-day binary retention limit issues.

[adriweb]

This can be closed, it was actually done in 5f8512f