eine

FTR, currently, in the CI jobs macOS builds use the same script as GNU/Linux builds. There are some differences, but the prodecure is to configure (mcode), make, make install, generate...

> Yes - I got your message - I'll take a look in March. > I'm a little busy with my Thesis and preparing for some conference workshops at the...

No worries!

@diogratia, that is probably because we are building the zipfiles (both mcode and LLVM) using `macos-latest`, which is `macos-10.15` (https://github.com/actions/virtual-environments/#available-environments). I can add a couple of jobs for running the...

Unfortunately, it seems that they disabled macos-11.0 temporaly. It works for orgs who had used it already, but new orgs/users are in a queue: https://github.com/actions/virtual-environments/issues/2486. Hence, tests fail: https://github.com/eine/ghdl/actions/runs/535662956. We'll...

My understanding is that they have many more machines/licenses for running Linux/Windows than they have for macos. So, while it's cheap for them to offer free resources in those platforms,...

> I'd be in favor of building on the [oldest MacOS practical](https://docs.travis-ci.com/user/reference/osx/#macos-version) to disenfranchise as few of potential Mac ghdl users as possible. In a year or so arm64 may...

Tarballs are updated automatically, and https://github.com/ghdl/setup-ghdl-ci uses fixed asset names for retrieving them and setting up CI. Therefore, having the specific version/sha in the tarball name is not an option....

I can analyze but not elaborate the provided MWE with a recent version of GHDL: ```sh # ghdl --version GHDL 1.0-dev (0.37.0.r1270.gb65ee8c3) [Dunoon edition] Compiled with GNAT Version: 10.2.0 llvm...

@Xiretza, I normally use the v1.0 milestone post-mortem. You will find that most issues are labeled but not milestoned until Tristan actually pushes some fix and closes it. That is,...