QBPE 3.6.0 compiler error

[madscijr]

What I would do:

Delete all previous 3.6 download attempts.
Download fresh.
Extract to your Desktop where you don't need setup permissions to use.
Do not white list.
Run the QB64pe.exe from your Desktop.

But I don't know what you did with Windows security, I'd try and undo it if the above does not work.

Thanks for your reply. I will give the desktop method a try, along with Jack's "setup_win.bat" method, and let you all know what happened.

[bplus]

Curious about Jack's "setup_win.bat" WTH? Sounds like something you need for Linux not Windows.

Anyway JUST follow my directions and you will be set in less than 10 minutes unless you've really monkeyed up Windows.

[DSMan195276]

A few clarifications:

1.

setup_win.bat

is only necessary if you download the source rather than a prebuilt release of QB64-PE for Windows. I would not recommend ever downloading a source version and just stick to the release versions, it's much harder for us to offer support if we don't know what exactly you have. Running

setup_win.bat

should work, but it should also be unnecessary.

2. Like Jack said do not mess with your

PATH

, that's just going to cause you problems and is unnecessary.

3. mingw32-make.exe is the name of the executable for

make

in both the 32-bit and 64-bit versions, it's expected.

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

.

[madscijr]

A few clarifications:
...
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

.

Thanks for your reply! 

It's not only possible there is another version of MinGW on my PC - there most definitely is, because I still have (and use) QB64 2.0.2. Is it possible to have both QB64 and QB64PE working side by side? 

I have some household chores to do now - as soon as I get a minute, I will look at the QB64PE config file, where I saw some path variable pointing to the compiler. Maybe I can point both QB64 & PE to the same folder.

[bplus]

How might we have both QB64 and QB64PE working side by side?

Don't mess with path:

[madscijr]

How might we have both QB64 and QB64PE working side by side?

Don't mess with path:

Right - I will un-mess with path!

[madscijr]

...
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.

TLDR: windows 11 sucks almost as bad as windows 8 did, definitely worse than vista and ME. (Anyone who wants to skip my Windows 11 rant, ignore the next couple paragrahs... sorry but MS makes me crazy sometimes)
<rant>I have had the displeasure of using a couple people's computers that either came with, or where in one case someone had the misfortune of upgrading to, Windows 11, and I hate it. Maybe not as much as Windows 8, but it's close. Actually, yes, I hate it that much, because by now, they should have learned not to try to reinvent the UI by removing features that people depend on. 
Like the task bar, which they pretty much destroyed, forcing us to combine taskbar buttons among other things that I have blocked from my memory. And where's my Quick Launch Toolbar?? Now where you could start an app with one click, it now takes 2 or 3. And where you could see in one place all your  open apps and windows, you now have to mouse over the icon to see what's open. 
And what's with this crap about forcing us to use OneDrive??? The thing is like a virus, you can't get it to go away!!!! 
WHY must they mess with good features and try to turn the OS into a wannabe Mac? Bring back Bill Gates, please!!!!! 
I will be avoiding Windows 11 for as long as humanly possible, or at least until they realize their mistakes and revert to the original taskbar, or restore the options to configure it to work like classic Windows (98, XP, 7). Like they did when they came to their senses and backtracked in Windows 8.1. Stop messing with perfection (well not perfection, but something I could at least use)!
Hell, if some genius would finally make a Linux distro that is a true Windows replacement, where the UI works exactly like Windows (same mouse pointer feel, same opening the start menu by pressing the start button where you can start typing to search the menu, same Run command, same menus and configuration, etc.) then I might become a regular Linux user. But so far, every Linux distro I have tried is aggravating as hell to use. Even Zorin OS, which was supposed to be almost "seamless" for Windows users to use, didn't even come close to that OS, and after hours of messing with configurations, I was no closer to getting it to behave how I want then when I started. 
But enough about me, what are you wearing? 

</rant>

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.

This was all because of a single folder (for the old QB64 2.0.2) in the system path! As soon as I removed it from the path, everything started working.

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.

I feel your pain. I still love and use Windows XP for various things. I have 3 different laptops running XP, and have all the system drives backed up with Clonezilla, so if an old laptop dies, I can find the same model on ebay, and restore the system! Back up, back up, back up!  

[madscijr]

Now it has to work! 

Try this simple fix and let us know what happens.  

I don't know why you're getting these errors.

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.

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

.

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.