Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GNU C++ Compiler error
#41
(Yesterday, 04:05 AM)eoredson Wrote:
(Yesterday, 03:26 AM)JRace Wrote: Hmmmmmn.

Okay, I'm out of ideas... except...  when was the last time you shut down Windows completely and restarted?

Windows can start acting flaky if you run it for too long without a full restart.  I once had a perfectly good compiler go bonkers and fail to create even the simplest executable.

Turned out it wasn't the compiler.  It was Windows, which I had left running for about a month.  I now try to remember to restart Windows at least once per week.
I normally restart Windows when a update icon on the taskbar indicates there is a update ready to install.

Otherwise I shutdown my computer Friday evening because I am not online on Saturdays..
Whelp, arghh.  Judging from the size of that compilelog.txt I'm guessing you are working with the 64-bit version.  Have you tried the 32-bit version?


(Yesterday, 03:44 AM)Cobalt Wrote: I haven't installed anything to my C drive since the days of DOS 3.11! if I have any choice in the matter (and yes there is some software out there that still gives you a choice) it goes elsewhere, heck at one time I didn't even install the OS to my C drive! tended to confuse the crap out of viruses and hackers when the C drive was empty! I knew if I found anything there it was time to reformat and reinstall.
any hoot...
Comp errors on a fresh clean install(unpacking the zip\rar\7z\ect. is in fact installing) can typically mean an issue with anti-virus(might as well call those viruses anymore) and\or permission issues.(need to kick MS programmers in the neither regions for that headache)
I just downloaded and tried both x86 and x64 versions and had no issue with PRINT "Hello World" anyway. Small issue with the extraction of the Archive but didn't seem to affect anything for compilation. installed in G:\, Running Windows 10 on a slightly beefy Ryzen 9 cpu.

LOL.

I've never hesitated to use the C: drive, but I NEVER do things the way MS intended.

I hate installers and only use them when there is no choice.  I've collected a set of small utilities that allow me to extract the files from most installers and test the software, then put it wherever I want.  If software won't run without an official installation, then I often decide I don't want it around.

Heck, I once experimented with making a thumbdrive-portable version of Jacob Navia's build of the LCC compiler.  For some unfathomable reason Navia built the compiler in the Microsoft way, using the Windows Registry to feed the compiler its essential location information.  Environment variables, Jacob, environment variables!  I FORCED that stupid build to work, using batch files to set the needed Registry keys, run the compiler, then delete the keys.  FWIW it was a (somewhat spiteful) proof of concept.  I have no need for THAT compiler.

I never use "Program Files" for manual "installs".  I have my own directory layout for that.  The neat thing about that arrangement is that I can zip the whole thing up and copy it to a new computer if/when it's needed, with my own self-written "install" utility to make the Start Menu & Send To links that I want.

"My Documents" is a dumping ground for stuff that I may or may not eventually email to someone.  I never touch any of the "My" folders unless some annoying piece of software forces me to.

   
Reply
#42
Quote:Judging from the size of that compilelog.txt I'm guessing you are working with the 64-bit version.  Have you tried the 32-bit version?
I have always strictly used the 32-bit version not having much luck with 64-bit at all.

Judging from the text in the log file it may be a bad build in the .7z but I am not sure.
Reply
#43
+1 and LOL @ My my my folder. I actually have one named My ASCII. Maybe I should try an merge it with my Fat32 folder. I just call it FAT.

Pete
Reply
#44
(Yesterday, 05:05 AM)Pete Wrote: +1 and LOL @ My my my folder. I actually have one named My ASCII. Maybe I should try an merge it with my Fat32 folder. I just call it FAT.

Pete
Maybe you should Sparse NTFS instead.
Reply
#45
Thanks, but if I need compression, Steve offered to throw me in his combine. I do love a good harvest festival!

Pete
Reply
#46
(Yesterday, 04:13 AM)eoredson Wrote: I am pretty sure it is not a virus detection or permission issue. In that case I rely on Defender to take care of detection..

But Ryzen 9 cpus are damn fast. What is your cpu speed at anyway? Mine runs up to 3.90 Ghz.

Found this on CoPilot:

The speed of a Ryzen 9 CPU can vary depending on the specific model. For example, the Ryzen 9 5900X has a base clock speed of 3.7 GHz and a boost clock speed of 4.8 GHz. Another model, the Ryzen 9 9900X, has a base clock speed of 4.4 GHz and a boost clock speed of up to 4.8 GHz

It is the Ryzen 9 7250X 16 core\ 32 thread running 4.5 capable of 5.7 boosted(1 core limit) 5.2 turbo(all 16 cores)
according to my hardware monitor it tends to ~5.5ghz a lot.
I was given a one time offer to splurge on this machine so I did. wasn't the top of line cpu but it was close(and I didn't really have $10k for the threadripper which was top of the line! at least this spring when I built this machine.)

[Image: hardware.jpg]

course now my CPU is ranked 75th I think it was 40s when I bought it, AMD introduced a lot of EPYC processors now.
the RTX 4070 has slipped from 5th to 21st in video card rankings.
Reply
#47
(Yesterday, 04:51 AM)eoredson Wrote:
Quote:Judging from the size of that compilelog.txt I'm guessing you are working with the 64-bit version.  Have you tried the 32-bit version?
I have always strictly used the 32-bit version not having much luck with 64-bit at all.

Judging from the text in the log file it may be a bad build in the .7z but I am not sure.

All those "warning: failed to compute relocation" warnings combined with all the "undefined symbol" errors suggest that the compiler is corrupted or incomplete.

Have you used the same .7z file on each attempt?  If so, you may want to re-download, or you could have 7Zip test the archive for errors.


These are the exact file sizes reported by Windows on my machine:
qb64pe_win-x64-4.0.0.7z  -  87,888,093
qb64pe_win-x86-4.0.0.7z  -  92,460,859

Here are the MD5 sums, if you need them:
QB64PE-4.0.0\qb64pe_win-x86-4.0.0.7z  -  5DD811BA631CEF9F02503F13F64E32CF
QB64PE-4.0.0\qb64pe_win-x64-4.0.0.7z  -  AA0087CD3E01813EBF8E743E49500ECD




EDIT: As per @Kernelpanic's response below, I recommend using ONLY the latest 7Zip on these archives if you aren't already.
Reply
#48
@Eoredson - Das Problem hatte ich auch min WinRAR 5.6. Nimm die neuste Version von 7z 24.09, dann auf die Zip-Datei mit Rechtsklick: "Öffnen mit 7z". Das funktioniert.

https://qb64phoenix.com/forum/showthread...5#pid30385
Reply
#49
(Yesterday, 06:39 PM)Kernelpanic Wrote: @Eoredson - Das Problem hatte ich auch min WinRAR 5.6. Nimm die neuste Version von 7z 24.09, dann auf die Zip-Datei mit Rechtsklick: "Öffnen mit 7z". Das funktioniert.

https://qb64phoenix.com/forum/showthread...5#pid30385
Huh, loosely translated:

Code: (Select All)
I also had the problem in WinRAR 5.6. Take the latest version of 7z 24.09, then on the zip file with right click: "Open with 7z". It works.
Reply
#50
(Yesterday, 06:34 PM)JRace Wrote:
(Yesterday, 04:51 AM)eoredson Wrote:
Quote:Judging from the size of that compilelog.txt I'm guessing you are working with the 64-bit version.  Have you tried the 32-bit version?
I have always strictly used the 32-bit version not having much luck with 64-bit at all.

Judging from the text in the log file it may be a bad build in the .7z but I am not sure.

All those "warning: failed to compute relocation" warnings combined with all the "undefined symbol" errors suggest that the compiler is corrupted or incomplete.

Have you used the same .7z file on each attempt?  If so, you may want to re-download, or you could have 7Zip test the archive for errors.


These are the exact file sizes reported by Windows on my machine:
qb64pe_win-x64-4.0.0.7z  -  87,888,093
qb64pe_win-x86-4.0.0.7z  -  92,460,859

Here are the MD5 sums, if you need them:
QB64PE-4.0.0\qb64pe_win-x86-4.0.0.7z  -  5DD811BA631CEF9F02503F13F64E32CF
QB64PE-4.0.0\qb64pe_win-x64-4.0.0.7z  -  AA0087CD3E01813EBF8E743E49500ECD




EDIT: As per @Kernelpanic's response below, I recommend using ONLY the latest 7Zip on these archives if you aren't already.
I checked the .7z filesizes and they are exactly the same and did a WinRar test file contents and there were no errors found.
Reply




Users browsing this thread: JRace, 4 Guest(s)