Peter

The source code seems to be quite old, for Dymola 2017 I assume. The file Cvode.c was updated from Sundials soon after that, so you could either try to fetch...

Using (and developers of) Dymola under Windows. We cannot see that this an obvious tool issue unfortunately. If you have a testbench with different compilers available, it would be good...

I realized the suggested modification will fail on systems where ```_POSIX_``` and ```__GNU__``` are both set. It instead needs to be: ``` #if defined(_POSIX_) int result = mkdir(directoryName, S_IRUSR |...

Ok, but you still need the ```|| defined(__GNUC__)``` on the line ``` #elif defined(__WATCOMC__) || defined(__LCC__) || defined(__GNUC__) ``` else MinGW will end up in the next condition and get...

Find attached the direct.h from 32-bit MinGW 15. Unclear why mkdir instead of _mkdir is used in this case. [direct.zip](https://github.com/user-attachments/files/20824430/direct.zip) It happens with MinGW 15 with gcc 15.1. It does...

A parital reply for now: * MinGW 15 is here: https://github.com/niXman/mingw-builds-binaries/releases * The ```The best matching gcc directory:...``` is just a warning message. You can workaround by renaming the folder...

> > * The `The best matching gcc directory:...` is just a warning message. You can workaround by renaming the folder "gcc510" to "gcc0510" > > If I only knew...

> > If you have any Dymola release from the latest years, you can reproduce by selecting MinGW 15 in the Simulation setup and then do > > ``` >...

> Anyway, could the original compilation issue be due to the unity/jumbo build of Dymola? I cannot with certainty exclude that the issue is Dymola specific although it did not...

Regarding what aspect? The naming convention for gcc folders?