Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QB64 Phoenix Edition v3.9.0 Released!
#41
@BSpinoza Glitch has been found in the source and we've got a patch for the issue. We're digging to make certain nothing else is out of whack, and we'll release a v3.9.1 with the fix in just a few days. Many thanks for reporting the issue.
Reply
#42
Quote:@BSpinoza -  Since QBPE64 version 3.9.0 the result is: inf
I get an error message from the compiler. According to the error log, apparently the c++ compiler is not found?  Huh

[Image: C-Fehler2023-10-07-140033.jpg]

"warning: =-Wl,--stack,26777216" -- This is my setting.

[Image: C-Einstellung2023-10-07-140119.jpg]


Attached Files
.txt   C++-Fehler_compilelog-07-10-2023.txt (Size: 1.84 KB / Downloads: 12)
Reply
#43
(10-07-2023, 05:44 AM)SMcNeill Wrote: @BSpinoza Glitch has been found in the source and we've got a patch for the issue. We're digging to make certain nothing else is out of whack, and we'll release a v3.9.1 with the fix in just a few days. Many thanks for reporting the issue.

I just downloaded 3.9, should I wait for 3.9.1 before unpacking and setting folder and reregistering the .exe for bas on Windows...? (It is not a trivial task setting up a new version.) I look forward to using Save Image without having to add library code.

To all the developers of QB64pe once again, Thank You! for keeping this project bug free and thriving with new abilities.
b = b + ...
Reply
#44
(10-07-2023, 01:12 PM)bplus Wrote:
(10-07-2023, 05:44 AM)SMcNeill Wrote: @BSpinoza Glitch has been found in the source and we've got a patch for the issue.  We're digging to make certain nothing else is out of whack, and we'll release a v3.9.1 with the fix in just a few days.  Many thanks for reporting the issue.

I just downloaded 3.9, should I wait for 3.9.1 before unpacking and setting folder and reregistering the .exe for bas on Windows...?  (It is not a trivial task setting up a new version.) I look forward to using Save Image without having to add library code.

To all the developers of QB64pe once again, Thank You! for keeping this project bug free and thriving with new abilities.

At this point, I'd wait for 3.9.1 before bothering to download and unpack.   We introduced about 3,214,179 bugs in 3.9.0 (a small exaggeration there, though it seemed it), with a fairly simply change, which have been addressed and corrected.  3.9.0 doesn't seem very reliable at all, math-wise, at the moment, so I'd hold off and wait for 3.9.1 which should be out by the end of the weekend, I'd imagine.  Smile
Reply
#45
That's right, the gamma program works under QB64 3.8.0. So, put everything back and wait for version 3.9.1.
Reply
#46
(10-07-2023, 02:03 PM)SMcNeill Wrote:
(10-07-2023, 01:12 PM)bplus Wrote:
(10-07-2023, 05:44 AM)SMcNeill Wrote: @BSpinoza Glitch has been found in the source and we've got a patch for the issue.  We're digging to make certain nothing else is out of whack, and we'll release a v3.9.1 with the fix in just a few days.  Many thanks for reporting the issue.

I just downloaded 3.9, should I wait for 3.9.1 before unpacking and setting folder and reregistering the .exe for bas on Windows...?  (It is not a trivial task setting up a new version.) I look forward to using Save Image without having to add library code.

To all the developers of QB64pe once again, Thank You! for keeping this project bug free and thriving with new abilities.

At this point, I'd wait for 3.9.1 before bothering to download and unpack.   We introduced about 3,214,179 bugs in 3.9.0 (a small exaggeration there, though it seemed it), with a fairly simply change, which have been addressed and corrected.  3.9.0 doesn't seem very reliable at all, math-wise, at the moment, so I'd hold off and wait for 3.9.1 which should be out by the end of the weekend, I'd imagine.  Smile

OK thanks!
b = b + ...
Reply
#47
Just a reminder. On Linux it is recommended to re-create "qb64pe" executable after a significant upgrade to the system! An example of such an "upgrade" is Debian "Bullseye" raised from v11.7 to v11.8. ("Bullseye" is now the "oldstable", while "Bookworm" has been the "stable" release for four months so far.)

With the Linux kernel, other components like "glibc" could be modified. This will ensure maximum compatibility with programs created by this programming system. The errors might be rare for LTS library mismatches but one doesn't ever want to be caught in that situation. Re-creating "qb64pe" executable could be more significant on the rolling-release distros such as Arch Linux, after somebody holds from updating for two months or longer.
Reply
#48
Since I deleted QB64 3.9 and reinstalled version 3.8.0, nothing works anymore. I keep getting this error message with every program:

[Image: C-Fehler2023-10-07-140033.jpg]


I've reinstalled QB64 3.8.0 six times now and tried everything I could think of. Rebooted three times, QB64 no longer works. Something have been completely bend.

Tomorrow I'll install 3.9.0 again and then uninstall it again. I've already experienced something like this: something went wrong the first time I uninstalled it, and then it worked again. But these programs were  registered in the registry file. And as a last resort, I will reset the system to October 6, 2023, which is the last restore point for me. Let's see.

At the moment I cannot use QB64.

The IDE doesn't even recognize its own files, even though they are displayed correctly in Explorer.

[Image: QB64-kann-bas-Datei-nicht-erkennen.jpg]
Reply
#49
You didn't extra and overwrite the old version did you?   That doesn't work.  You need to extract to a new, clean folder.
Reply
#50
(10-07-2023, 09:52 PM)SMcNeill Wrote: You didn't extra and overwrite the old version did you?   That doesn't work.  You need to extract to a new, clean folder.
No, I didn't overwrite it, I never do that! I know the problems.
I also installed QB64 3.8 to another folder, same result. I have never experienced anything like this before. I'm at a loss! In moment.

Tomorrow I'll try what I mentioned.
Reply




Users browsing this thread: 2 Guest(s)