(03-21-2023, 04:28 PM)Kernelpanic Wrote: Now it has to work!
(03-21-2023, 04:30 PM)SMcNeill Wrote: Try this simple fix and let us know what happens.
(03-22-2023, 05:36 PM)mnrvovrfc Wrote: I don't know why you're getting these errors.
(03-21-2023, 03:32 PM)Jack Wrote: 3: double-click on setup_win.bat
Thanks everyone for your replies and advice. It wasn't permissions, and it wasn't configuration.
I didn't have to compile my own - although I think Jack may have taught a few of us some new tricks.
It was the path, and multiple copies of mingw.
(03-23-2023, 01:55 AM)DSMan195276 Wrote: 4. Is it possible you have another version of MinGW installed on your machine? Errors like the `-auxbase-strip` thing are related to the `cc1plus.exe` not understanding internal parameters passed to it from the main `g++.exe`. AFAIK this should never happen as long as the `cc1plus.exe` and `g++.exe` are from the same version of MinGW. Check that you don't have something like a `C:\MinGW\` folder, and check your `PATH` for anything that looks related to `MinGW`.
(03-23-2023, 02:47 AM)bplus Wrote:Quote:How might we have both QB64 and QB64PE working side by side?
Don't mess with path:
That was it!!! DSMan195276 asking about multiple copies of mingw got me thinking that maybe having 2 different QB64 editions, both using mingw, could be confusing things. The QB64 2.0.2 folder location was in my path from way back - I don't even recall why I originally added it, but once I removed that, QB64PE started working (and QB64 2.0.2 still works).
Thanks bplusplus (you have earned an extra +) and thanks DSMan195276.
Don't mess with path!
Let that be a motto.