The --enable-blockerupter option is listed in the readme on the cgminer GitHub. That is not what the problem is.

On the readme the developer states that cgminer is guaranteed to be more stable on a linux based OS, not that it will run better. Performance should be similar across both platforms.

EDIT: Forgot to mention that the article you linked isn't useful to me because I am using MXE (which is what the developer recommends as a cross compilation tool) to compile cgminer

0bit, I totally agree with os2sam. I was one of the people who was having trouble running newpacs on a Win10 pc. I helped get some data together for vh (who developed the “gekko” version of cgminer) to try and get things running stable on Windows machines but it was a PITA. I ended up getting a Pi4 (not a pi3) as it was the best for running them on. They are even tested on Linux machines by the manufacturer.

Performance will be BETTER and it will run BETTER on a linux based OS. The reason being, the asic boost feature of vh’s cgminer will run properly on a linux OS, on a windows machine it wont so you wont reach the potential peak hashrate. Also I found that it would constantly restart the sticks and I ended up running out of USB com ports so eventually they would all stop working on Win10.

But if you are insistent on cross compiling it then feel free to waste your time.

---

Update on my issues:

So ive been testing it over the past couple of days and it seems to run for almost 24hours on V5 at 600-650m. But seems to always cut out. I've switched it down to 575m V5 to try and run it at almost stock clocks to see how it goes. One thing I have noticed is that it is ALWAYS "chip 0" which doesnt like  the freq. sidehack, would this possibly be the "12 slow" that was marked on the pcb or is that the other end of the string?

No worries. It seems that chip 0 always wants to be one step below whatever freq I set it at. I've got another unit on the way which hopefully wont be too long. I may take a closer look at it once it arrives. Do the heatsinks come off at all? I haven't tried yet but didn't notice anything on the areas I could see.

EDIT, Update:
She's been running at 550m V5 for the past couple of days, tried 575m but didnt like it. It seems thats all the puff she has now. At least shes stable though 

My two R606's are pulling 207 Watts, including the Power Supply and minus the Pi 4.

Both are running 725Mhz, one power level 5 and the other power level 6 for a total of 1.94THs.

Got a couple of high end ones there then. I’ve just received my second/replacement and working on building it up to 1th (or close).

I googled it and found a picture. But it would be handy if the first post pics were back up.

I'll probably fix it sometime. I tended to lean on my webserver for image hosting but the connection was fairly slow so I also used photobucket. The server's now set up in an actual data center with a solid connection so I should port everything over to it.

I know its daunting looking through the 80 pages of posts. Maybe Sidehack/VH can update the first page with all the config settings cgminer now supports?

you may want to try --gekko-start-freq, I havent gone through the code on github to see if it works for terminus but it would be worth a quick try. like you said, letting it autotune is best, but this is the one your looking for: --gekko-tune-down

https://bt.irlbtc.com/view/5053833.msg50506833#msg50506833

 [90-95]% is a healthy range, 95 is default, set to 0 to disable.
        1.  Adjusts frequency according to each miner's unique charateristics
        2.  To keep a hash performance above 95%.
        3.  Based on the idea that (95% of 275MHz) hashes better than (80% of 300MHz)