2024-01-11 01:55 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Il 11/01/2024 07:56, Ron Pinkas ha scritto:
2024-01-11 01:55 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Sorry, I still get this:
cc1.exe: error: CPU you selected does not support x86-64 instruction set mingw32-make: *** [winmake/compile.mak:374: obj\gc64\hbrmw64.o] Error 1
cc1.exe: error: CPU you selected does not support x86-64 instruction set
mingw32-make: *** [winmake/compile.mak:374: obj\gc64\hbrmw64.o] Error 1
You are not using CLang Enrico. I will soon post a guide.
Enrico Maria Giordano wrote:
Il 11/01/2024 07:56, Ron Pinkas ha scritto:
2024-01-11 01:55 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Sorry, I still get this:
cc1.exe: error: CPU you selected does not support x86-64 instruction set mingw32-make: *** [winmake/compile.mak:374: obj\gc64\hbrmw64.o] Error 1
You are not using CLang Enrico. I will soon post a guide.
Il 11/01/2024 16:44, Ron Pinkas ha scritto:
cc1.exe: error: CPU you selected does not support x86-64 instruction set mingw32-make: *** [winmake/compile.mak:374: obj\gc64\hbrmw64.o] Error 1
You are not using CLang Enrico. I will soon post a guide.
So we do not support MinGW not-CLANG anymore? If yes, why?
So we do not support MinGW not-CLANG anymore? If yes, why?
I did not touch MingW I only ADDED support for CLang
You are not using CLang Enrico. I will soon post a guide.
This is the TRUE Clang for Windows - with minimal Mingw-w64 support:
https://github.com/mstorsjo/llvm-mingw
Il 11/01/2024 07:56, Ron Pinkas ha scritto:
2024-01-11 01:55 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Sorry, I still get this:
cc1.exe: error: CPU you selected does not support x86-64 instruction set mingw32-make: *** [winmake/compile.mak:374: obj\gc64\hbrmw64.o] Error 1
Which batch file do you use?
Il 11/01/2024 20:00, Ron Pinkas ha scritto:
Which batch file do you use?
SET CC_DIR=e:\fw\temp\mgw64
make_gc64 all
SET CC_DIR=e:\fw\temp\mgw64
make_gc64 all
I don'tt have to test but will post tentative fix shorttly.
Il 11/01/2024 19:04, Ron Pinkas ha scritto:
You are not using CLang Enrico. I will soon post a guide.
This is the TRUE Clang for Windows - with minimal Mingw-w64 support:
https://github.com/mstorsjo/llvm-mingw
I have no clue about what to do with it, sorry. :-(
Download and unzip to C: drive (required for now) using default folder.
https://github.com/mstorsjo/llvm-mingw/releases/download/20231128/llvm-mingw-20231128-ucrt-x86_64.zip
For now you also need your xharbour directory to be on the C: drive.
Then in xharbour directtory just type make_clng.bat.
Il 11/01/2024 21:58, Ron Pinkas ha scritto:
SET CC_DIR=e:\fw\temp\mgw64
make_gc64 all
I don'tt have to test but will post tentative fix shorttly.
And I will glad to test it, thank you.
Might be resolved by 2024-01-13 00:32 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Il 13/01/2024 06:35, Ron Pinkas ha scritto:
Might be resolved by 2024-01-13 00:32 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Yes, now MGW32 and MGW64 (not-CLANG) build without errors. But two notes:
- the names of the 64 bit LIBs don't have the 64 anymore. Example:
libcommon64.a -> libcommon.a
- there are many warnings in the contribs like these:
source\compiler\harbour.c:2286:62: warning: bitwise comparison always evaluates to false [-Wtautological-compare]
obj\gc64\comptool.c:478:24: warning: format '%u' expects argument of
type 'unsigned int', but argument 8 has type 'HB_SIZE' {aka 'long long unsigned int'} [-Wformat=]
include/hbapi.h:211:28: warning: missing braces around initializer [-Wmissing-braces]
Should they silenced?
Yes, now MGW32 and MGW64 (not-CLANG) build without errors. But two notes:
- the names of the 64 bit LIBs don't have the 64 anymore. Example:
libcommon64.a -> libcommon.a
Yes this is intentional, instead different architectures have their own
sub dir, just like different compiler - since they arejust as
incompatible.
- there are many warnings in the contribs like these:
source\compiler\harbour.c:2286:62: warning: bitwise comparison always
evaluates to false [-Wtautological-compare]
obj\gc64\comptool.c:478:24: warning: format '%u' expects argument of
type 'unsigned int', but argument 8 has type 'HB_SIZE' {aka 'long long
unsigned int'} [-Wformat=]
include/hbapi.h:211:28: warning: missing braces around initializer
[-Wmissing-braces]
Should they silenced?
Preferbly reviewed and fixed - but we must be very careful - "fixing" warnings can just as easy cause real bugs.
Unfortunately, MSC32, MSC64 and BCC32 build don't work anymore. :-(
For your convenience xHarbour's bin directory was added to your PATH.
"ERROR: Microsoft C/C++ not found!"
---------------------------------------
Make Utility for Microsoft C/C++
---------------------------------------
Microsoft C/C++ not found.
Please install and try again.
My batch:
SET CC_DIR=e:\msc32\msc
make_vc all
Il 13/01/2024 16:49, Ron Pinkas ha scritto:
Yes, now MGW32 and MGW64 (not-CLANG) build without errors. But two notes:
- the names of the 64 bit LIBs don't have the 64 anymore. Example:
libcommon64.a -> libcommon.a
Yes this is intentional, instead different architectures have their own
sub dir, just like different compiler - since they arejust as
incompatible.
Ok, perfect. Is this true for all the other compilers? No more "64" distinction in the LIBs names? At this time I can't test them because,
as I reported, they can't be built now.
- there are many warnings in the contribs like these:
source\compiler\harbour.c:2286:62: warning: bitwise comparison always evaluates to false [-Wtautological-compare]
obj\gc64\comptool.c:478:24: warning: format '%u' expects argument of
type 'unsigned int', but argument 8 has type 'HB_SIZE' {aka 'long long unsigned int'} [-Wformat=]
include/hbapi.h:211:28: warning: missing braces around initializer [-Wmissing-braces]
Should they silenced?
Preferbly reviewed and fixed - but we must be very careful - "fixing" warnings can just as easy cause real bugs.
They are contribs warnings, so, as you said recently, it should left untouched, or am I wrong?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 399 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 66:43:39 |
| Calls: | 8,355 |
| Calls today: | 15 |
| Files: | 13,159 |
| Messages: | 5,894,218 |
| Posted today: | 1 |