03-22-2023, 05:36 PM
I wish those people in charge of MinGW straightened out how they name their stuff.
What is "mingw32-make"? This seems to be the 32-bit edition of "make" utility. If you're on a 64-bit system then all programs without exception are supposed to be 64-bit. Nothing which is 32-bit should get in the way. So this might be a fault with the packaging of QB64PE.
Also, Scooby-Doo and gang, solve the mystery of "-auxbase-strip" switch that other time...
I don't know why you're getting these errors. I haven't upgraded to Windows11 so I wouldn't know how using that system is like. But in the few times I've gone into Windows in the past six months and used QB64PE I didn't have these problems. I was able to use the 64-bit edition apart from the 32-bit edition. I had to use the 32-bit edition only for eoredson's SICK64, that was the only reason for it to exist. This is after one of my laptops which is over 15 years old finally had its hard drive die with WindowsXP in it.
What is "mingw32-make"? This seems to be the 32-bit edition of "make" utility. If you're on a 64-bit system then all programs without exception are supposed to be 64-bit. Nothing which is 32-bit should get in the way. So this might be a fault with the packaging of QB64PE.
Also, Scooby-Doo and gang, solve the mystery of "-auxbase-strip" switch that other time...
I don't know why you're getting these errors. I haven't upgraded to Windows11 so I wouldn't know how using that system is like. But in the few times I've gone into Windows in the past six months and used QB64PE I didn't have these problems. I was able to use the 64-bit edition apart from the 32-bit edition. I had to use the 32-bit edition only for eoredson's SICK64, that was the only reason for it to exist. This is after one of my laptops which is over 15 years old finally had its hard drive die with WindowsXP in it.