@a740g @SMcNeill @RhoSigma
Hello the qb64pe devs' team.
As I mentioned in a previous post, I couldn't install qb64pe version 4.3.0 on my 27-inch iMac running macOS 10.13.6 because its setup_osx.command uses a newer version of gcc that isn't available with Xcode 10.1, making it unusable with this version of macOS (High Sierra).
True and False!
What's False?
In fact, this version of qb64pe (4.3.0) could work under High Sierra as you can see on my High Sierra desktop' screen-shot below showing both the macOS and qb64pe "about" panels (above my personnal iMac Dev's wallpaper) !
![[Image: High-Sierra-Screen-Shot.png]](http://iss2you.ddns.net/pictures/High-Sierra-Screen-Shot.png)
But there's a trick to making it work!
What's True?
The failled install is due to a "setting" in the compilation method that calls the wrong compiler version.
What's the trick?
Note:
My three 27-inch iMacs are well-configured with a 3.4 GHz i7 processor, 32 GB of RAM, and one SSD of varying capacities. My Mac Mini 2 Server, on the other hand, is equipped with a 2.4 GHz i7 processor, 16 GB of RAM, and a 2 TB SSD. These are older, inexpensive machines, all manufactured in 2012. Yet, they work perfectly, just like they did on day one, and that's precisely why I've only used Apple systems since my retirement: their reliability is undeniable! And noaday, you can find them used for between $250 and $500, depending on their CPU, GPU, RAM, and SSD configuration.
Since I'm real stubborn, and because of the numerous paid programs I've installed on macOS High Sierra (which is the reason I keep it as my OS of choice), I spent this last weekend downloading all versions of qb64pe from 3.0.0 to 4.3.0, then installing them all (each in a separate directory) and testing them all on my development 27-inch iMac (with its fast internal Crucial 4Tb SDD), including version 4.2.0, which installed and works like a charm!
So, I decided to compil the qb64pe.bas file located in the source directory of the version 4.3.0 directly from the IDE of the version 4.2.0 using the option "Output EXE to Source Folder" and lo and behold, not only the executable was created perfectly, but launched too!
I then copied the 2 files (qb64pe and qb64pe_start.command,) which had been created in the "source" directory of qb64pe-4.3.0, into the main directory of this version (4.3.0), and now qb64pe-4.3.0 could work on macOS High Sierra if you can also solve the Second problem below
Therefore, I don't know which parameter(s) were modified, nor where they are located in the compilation method of this version 4.3.0 compared to that of qb64pe 4.2.0 (ending with a nice "Launching 'QB64-PE'), which causes the execution of the 4.3.0 bash installation script to end with a subset of the following error messages:
So, could you please fix this problem by checking from a terminal session what macOS version "cw-vers -productVersion"
and what Xcode version "pkgutil --pkg-info=com.apple.pkg.CLTools_Executables" are running,
then choosing the right Xcode command line call to use accordingly?
Second problem:
If Qb64PE 4.3.0 can load, it cannot compile and returns the error message: C++ Compilation failed (Check ./internal/temp/compilelog.txt)
So, could you please fix this second problem that should be done with the right installation as requested above.
I bet this would help for future qb64pe releases running old macOS releases too.
Cheers.
Fifi
Hello the qb64pe devs' team.
As I mentioned in a previous post, I couldn't install qb64pe version 4.3.0 on my 27-inch iMac running macOS 10.13.6 because its setup_osx.command uses a newer version of gcc that isn't available with Xcode 10.1, making it unusable with this version of macOS (High Sierra).
True and False!
What's False?
In fact, this version of qb64pe (4.3.0) could work under High Sierra as you can see on my High Sierra desktop' screen-shot below showing both the macOS and qb64pe "about" panels (above my personnal iMac Dev's wallpaper) !
But there's a trick to making it work!
What's True?
The failled install is due to a "setting" in the compilation method that calls the wrong compiler version.
What's the trick?
Note:
My three 27-inch iMacs are well-configured with a 3.4 GHz i7 processor, 32 GB of RAM, and one SSD of varying capacities. My Mac Mini 2 Server, on the other hand, is equipped with a 2.4 GHz i7 processor, 16 GB of RAM, and a 2 TB SSD. These are older, inexpensive machines, all manufactured in 2012. Yet, they work perfectly, just like they did on day one, and that's precisely why I've only used Apple systems since my retirement: their reliability is undeniable! And noaday, you can find them used for between $250 and $500, depending on their CPU, GPU, RAM, and SSD configuration.
Since I'm real stubborn, and because of the numerous paid programs I've installed on macOS High Sierra (which is the reason I keep it as my OS of choice), I spent this last weekend downloading all versions of qb64pe from 3.0.0 to 4.3.0, then installing them all (each in a separate directory) and testing them all on my development 27-inch iMac (with its fast internal Crucial 4Tb SDD), including version 4.2.0, which installed and works like a charm!
So, I decided to compil the qb64pe.bas file located in the source directory of the version 4.3.0 directly from the IDE of the version 4.2.0 using the option "Output EXE to Source Folder" and lo and behold, not only the executable was created perfectly, but launched too!
I then copied the 2 files (qb64pe and qb64pe_start.command,) which had been created in the "source" directory of qb64pe-4.3.0, into the main directory of this version (4.3.0), and now qb64pe-4.3.0 could work on macOS High Sierra if you can also solve the Second problem below
Therefore, I don't know which parameter(s) were modified, nor where they are located in the compilation method of this version 4.3.0 compared to that of qb64pe 4.2.0 (ending with a nice "Launching 'QB64-PE'), which causes the execution of the 4.3.0 bash installation script to end with a subset of the following error messages:
Code: (Select All)
errorerror: : invalidinvalid valuevalue 'gnu++20''gnu++20' inin '-std=gnu++20''-std=gnu++20'
notenote: : useuse 'c++98''c++98' oror 'c++03''c++03' forfor 'ISO C++ 1998 with amendments''ISO C++ 1998 with amendments' standardstandard
notenote: : useuse 'gnu++98''gnu++98' oror 'gnu++03''gnu++03' forfor 'ISO C++ 1998 with amendments and GNU extensions''ISO C++ 1998 with amendments and GNU extensions' standardstandard
notenote: : use use'c++11' 'c++11'for for'ISO C++ 2011 with amendments' 'ISO C++ 2011 with amendments'standard standard
note: use note'gnu++11': foruse 'ISO C++ 2011 with amendments and GNU extensions''gnu++11' standardfor
'ISO C++ 2011 with amendments and GNU extensions' standardnote
: use note'c++14': foruse 'ISO C++ 2014 with amendments''c++14' standardfor
'ISO C++ 2014 with amendments' standardnote
: use note'gnu++14': foruse 'ISO C++ 2014 with amendments and GNU extensions''gnu++14' standardfor
'ISO C++ 2014 with amendments and GNU extensions' standard
note: usenote : 'c++17' usefor 'c++17''ISO C++ 2017 with amendments' forstandard 'ISO C++ 2017 with amendments'
standard
note: noteuse: 'gnu++17'use for'gnu++17' for'ISO C++ 2017 with amendments and GNU extensions' 'ISO C++ 2017 with amendments and GNU extensions'standard standard
notenote: : useuse 'c++2a''c++2a' forfor 'Working draft for ISO C++ 2020''Working draft for ISO C++ 2020' standardstandard
notenote: : error: useuse 'gnu++2a''gnu++2a' invalidforfor 'Working draft for ISO C++ 2020 with GNU extensions''Working draft for ISO C++ 2020 with GNU extensions'value standardstandard'gnu++20'
in '-std=gnu++20'
note: use 'c++98' or 'c++03' for 'ISO C++ 1998 with amendments' standard
note: use 'gnu++98' or 'gnu++03' for 'ISO C++ 1998 with amendments and GNU extensions' standard
note: use 'c++11' for 'ISO C++ 2011 with amendments' standard
note: use 'gnu++11' for 'ISO C++ 2011 with amendments and GNU extensions' standard
note: use 'c++14' for 'ISO C++ 2014 with amendments' standard
note: use 'gnu++14' for 'ISO C++ 2014 with amendments and GNU extensions' standard
note: use 'c++17' for 'ISO C++ 2017 with amendments' standard
note: use 'gnu++17' for 'ISO C++ 2017 with amendments and GNU extensions' standard
note: use 'c++2a' for 'Working draft for ISO C++ 2020' standard
note: use 'gnu++2a' for 'Working draft for ISO C++ 2020 with GNU extensions' standard
make: *** [internal/c/libqb/src/threading.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [internal/c/qbx.o] Error 1
make: *** [internal/c/libqb_make_00010100.o] Error 1
Compilation of QB64-PE failed!So, could you please fix this problem by checking from a terminal session what macOS version "cw-vers -productVersion"
and what Xcode version "pkgutil --pkg-info=com.apple.pkg.CLTools_Executables" are running,
then choosing the right Xcode command line call to use accordingly?
Second problem:
If Qb64PE 4.3.0 can load, it cannot compile and returns the error message: C++ Compilation failed (Check ./internal/temp/compilelog.txt)
Code: (Select All)
c++ -std=gnu++20 -fno-strict-aliasing -Wno-conversion-null -I./internal/c/libqb/include -I./internal/c/parts/core/freeglut/include -I./internal/c/parts/core/glew/include -DDEPENDENCY_NO_SOCKETS -DDEPENDENCY_NO_PRINTER -DDEPENDENCY_NO_ICON -DDEPENDENCY_NO_SCREENIMAGE internal/c/libqb.cpp -c -o internal/c/libqb_make_00000000.o
error: invalid value 'gnu++20' in '-std=gnu++20'
note: use 'c++98' or 'c++03' for 'ISO C++ 1998 with amendments' standard
note: use 'gnu++98' or 'gnu++03' for 'ISO C++ 1998 with amendments and GNU extensions' standard
note: use 'c++11' for 'ISO C++ 2011 with amendments' standard
note: use 'gnu++11' for 'ISO C++ 2011 with amendments and GNU extensions' standard
note: use 'c++14' for 'ISO C++ 2014 with amendments' standard
note: use 'gnu++14' for 'ISO C++ 2014 with amendments and GNU extensions' standard
note: use 'c++17' for 'ISO C++ 2017 with amendments' standard
note: use 'gnu++17' for 'ISO C++ 2017 with amendments and GNU extensions' standard
note: use 'c++2a' for 'Working draft for ISO C++ 2020' standard
note: use 'gnu++2a' for 'Working draft for ISO C++ 2020 with GNU extensions' standard
make: *** [internal/c/libqb_make_00000000.o] Error 1So, could you please fix this second problem that should be done with the right installation as requested above.
I bet this would help for future qb64pe releases running old macOS releases too.
Cheers.
Fifi
Before to send the arrow of truth, dip the head in a honey pot (Cheyenne saying).
Don't tell my Mom I'm on iMac with macOS, she thinks I work on PC with Windows.