Enrico, can you please provide your full status report after this last
commit?
BCC32 OK!
2024-01-06 13:50 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
* winmake/find_pc.bat
* winmake/find_vc.bat
* Synched the latest modification of REM fix.
Enrico, can you please provide your full status report after this last commit?
2024-01-06 13:50 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
* winmake/find_pc.bat
* winmake/find_vc.bat
* Synched the latest modification of REM fix.
Enrico, can you please provide your full status report after this last commit?
A little problem with BCC64:
For your convenience xHarbour's bin directory was added to your PATH.
"ELSE" non è riconosciuto come comando interno o esterno,
 un programma eseguibile o un file batch.
I can't build xharbour with bcc32 7.73, there are the folloing errors:
Please try after: 2024-01-06 15:45 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Enrico, can you please provide your full status report after this last commit?
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc. Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 238: Expression syntax error in !if statement
Error winmake\makefile.bc 247: Expression syntax error in !if statement
Error winmake\makefile.bc 253: Expression syntax error in !if statement
Error winmake\makefile.bc 266: Expression syntax error in !if statement
*** 6 errors during make ***
With bcc32c 7.73 it compiles without any error.
Thanks,
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail. www.avg.com
Enrico, can you please provide your full status report after this last commit?
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc. Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 238: Expression syntax error in !if statement
Error winmake\makefile.bc 247: Expression syntax error in !if statement
Error winmake\makefile.bc 253: Expression syntax error in !if statement
Error winmake\makefile.bc 266: Expression syntax error in !if statement
*** 6 errors during make ***
With bcc32c 7.73 it compiles without any error.
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc. >> Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 238: Expression syntax error in !if statement
Error winmake\makefile.bc 247: Expression syntax error in !if statement
Error winmake\makefile.bc 253: Expression syntax error in !if statement
Error winmake\makefile.bc 266: Expression syntax error in !if statement
*** 6 errors during make ***
With bcc32c 7.73 it compiles without any error.
Mmm, those lines appear normal - can you check what is the value of
BCC_LIB? Please postt your funcions.log after such failure.
Ron,
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc.
Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 238: Expression syntax error in !if statement Error winmake\makefile.bc 247: Expression syntax error in !if statement Error winmake\makefile.bc 253: Expression syntax error in !if statement Error winmake\makefile.bc 266: Expression syntax error in !if statement *** 6 errors during make ***
With bcc32c 7.73 it compiles without any error.
Mmm, those lines appear normal - can you check what is the value of BCC_LIB? Please postt your funcions.log after such failure.
here is the funtions.log:
*** START [C:\Users\rhfsy\xharbour\make_bc.bat](all)
*** started [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** started(bcc32) [C:\Users\rhfsy\xharbour\winmake\found_cc.bat]
*** Raw Arguments: (strLen CC_DIR _CC_DIR_LEN)
*** Raw Arguments: [strLen] [CC_DIR] [_CC_DIR_LEN] [] []
*** Parsed [2] :strLen( CC_DIR=c:\borland\BCC770 _CC_DIR_LEN=18 )
+++ Entry point: strLen('CC_DIR' '_CC_DIR_LEN')(2)
:strLen(CC_DIR _CC_DIR_LEN)
:isValidVarName(_CC_DIR_LEN)
:value(CC_DIR str)
:isValidVarName(str)
--- Exit point: strLen CC_DIR _CC_DIR_LEN
*** Ret: 0 0
*** ended[0] [C:\Users\rhfsy\xharbour\winmake\found_cc.bat]
*** finished[0] [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** END [C:\Users\rhfsy\xharbour\make_bc.bat]
*** START [C:\Users\rhfsy\xharbour\make_bc.bat](all)
*** started [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** started(bcc32) [C:\Users\rhfsy\xharbour\winmake\found_cc.bat]
*** Raw Arguments: (strLen CC_DIR _CC_DIR_LEN)
*** Raw Arguments: [strLen] [CC_DIR] [_CC_DIR_LEN] [] []
*** Parsed [2] :strLen( CC_DIR=c:\borland\BCC770 _CC_DIR_LEN=18 )
+++ Entry point: strLen('CC_DIR' '_CC_DIR_LEN')(2)
:strLen(CC_DIR _CC_DIR_LEN)
:isValidVarName(_CC_DIR_LEN)
:value(CC_DIR str)
:isValidVarName(str)
--- Exit point: strLen CC_DIR _CC_DIR_LEN
*** Ret: 0 0
*** ended[0] [C:\Users\rhfsy\xharbour\winmake\found_cc.bat]
*** finished[0] [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** END [C:\Users\rhfsy\xharbour\make_bc.bat]
Thx. What is the value of BCC_LIB?
Thx. What is the value of BCC_LIB?
How can I see the value of BCC_LIB?
You are correct! The BCC_LIB is empty.
I Set a value to it and It compiled fine!
If you start a clean terminal then bcc_lib should be generated for you.
Also even if its empty it shoul not cause an error - we need to debug
this.
Ron
Ron,
Thx. What is the value of BCC_LIB?
How can I see the value of BCC_LIB?
You are correct! The BCC_LIB is empty.
I Set a value to it and It compiled fine!
Thanks
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail. www.avg.com
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43Â Copyright (c) 1987, 2019 Embarcadero Technologies, Inc. Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 238: Expression syntax error in !if statement
Error winmake\makefile.bc 247: Expression syntax error in !if statement
Error winmake\makefile.bc 253: Expression syntax error in !if statement
Error winmake\makefile.bc 266: Expression syntax error in !if statement
*** 6 errors during make ***
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43Â Copyright (c) 1987, 2019 Embarcadero Technologies,
Inc.
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 234: Expression syntax error in !if statement
Error winmake\makefile.bc 238: Expression syntax error in !if statement
Error winmake\makefile.bc 247: Expression syntax error in !if statement
Error winmake\makefile.bc 253: Expression syntax error in !if statement
Error winmake\makefile.bc 266: Expression syntax error in !if statement
*** 6 errors during make ***
Strange, I get no errors building with BCC32 7.70 (NO CLANG).
I still get these errors building with BCC64 7.70 (CLANG):
Strange, I get no errors building with BCC32 7.70 (NO CLANG).
I still get these errors building with BCC64 7.70 (CLANG):
    ilink64 -ap -Tpe -x -Gn -C -Llib\bc64 -Le:\fw\temp\bcc64\bcc\lib;e:\fw\temp\bcc64\bcc\lib\psdk c0x64.o obj\bc64\mainstd.o obj\bc64\xbscript.o ,bin\bc64\xbscript.exe,, lib\bc64\pp.a lib\bc64\common.a lib\bc64\debug.a lib\bc64\vm.a lib\bc64\rtl.a lib\bc64\pcrepos.a lib\bc64\gtwin.a lib\bc64\lang.a lib\bc64\rdd.a lib\bc64\macro.a lib\bc64\dbffpt.a lib\bc64\redbffpt.a
 lib\bc64\dbfntx.a lib\bc64\dbfnsx.a lib\bc64\dbfcdx.a lib\bc64\dbfmdx.a lib\bc64\bmdbfcdx.a lib\bc64\redbfcdx.a lib\bc64\sixcdx.a lib\bc64\bmsixcdx.a lib\bc64\hbsix.a lib\bc64\hsx.a
 lib\bc64\usrrdd.a lib\bc64\rdds.a lib\bc64\codepage.a lib\bc64\ct.a
 lib\bc64\zlib.a  ws2_32.a cw64mt.a import64.a
Turbo Incremental Link64 6.98 Copyright (c) 1997-2023 Embarcadero Technologies, Inc.
Error: Unresolved external 'HB_FUN_DLLPREPARECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLUNLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_SETLASTERROR' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_GETPROCADDRESS' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLEXECUTECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLCALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Il 06/01/2024 23:47, Enrico Maria Giordano ha scritto:
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc.
Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 238: Expression syntax error in !if statement Error winmake\makefile.bc 247: Expression syntax error in !if statement Error winmake\makefile.bc 253: Expression syntax error in !if statement Error winmake\makefile.bc 266: Expression syntax error in !if statement *** 6 errors during make ***
Strange, I get no errors building with BCC32 7.70 (NO CLANG).
I still get these errors building with BCC64 7.70 (CLANG):
ilink64 -ap -Tpe -x -Gn -C -Llib\bc64 -Le:\fw\temp\bcc64\bcc\lib;e:\fw\temp\bcc64\bcc\lib\psdk c0x64.o obj\bc64\mainstd.o obj\bc64\xbscript.o ,bin\bc64\xbscript.exe,, lib\bc64\pp.a lib\bc64\common.a lib\bc64\debug.a lib\bc64\vm.a lib\bc64\rtl.a lib\bc64\pcrepos.a lib\bc64\gtwin.a lib\bc64\lang.a lib\bc64\rdd.a lib\bc64\macro.a lib\bc64\dbffpt.a lib\bc64\redbffpt.a
lib\bc64\dbfntx.a lib\bc64\dbfnsx.a lib\bc64\dbfcdx.a
lib\bc64\dbfmdx.a lib\bc64\bmdbfcdx.a lib\bc64\redbfcdx.a
lib\bc64\sixcdx.a lib\bc64\bmsixcdx.a lib\bc64\hbsix.a lib\bc64\hsx.a
lib\bc64\usrrdd.a lib\bc64\rdds.a lib\bc64\codepage.a lib\bc64\ct.a lib\bc64\zlib.a ws2_32.a cw64mt.a import64.a
Turbo Incremental Link64 6.98 Copyright (c) 1997-2023 Embarcadero Technologies, Inc.
Error: Unresolved external 'HB_FUN_DLLPREPARECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLUNLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_SETLASTERROR' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_GETPROCADDRESS' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLEXECUTECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLCALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Il 06/01/2024 23:47, Enrico Maria Giordano ha scritto:
I can't build xharbour with bcc32 7.73, there are the folloing errors:
MAKE Version 5.43 Copyright (c) 1987, 2019 Embarcadero Technologies, Inc.
Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 234: Expression syntax error in !if statement Error winmake\makefile.bc 238: Expression syntax error in !if statement Error winmake\makefile.bc 247: Expression syntax error in !if statement Error winmake\makefile.bc 253: Expression syntax error in !if statement Error winmake\makefile.bc 266: Expression syntax error in !if statement *** 6 errors during make ***
Strange, I get no errors building with BCC32 7.70 (NO CLANG).
I still get these errors building with BCC64 7.70 (CLANG):
ilink64 -ap -Tpe -x -Gn -C -Llib\bc64 -Le:\fw\temp\bcc64\bcc\lib;e:\fw\temp\bcc64\bcc\lib\psdk c0x64.o obj\bc64\mainstd.o obj\bc64\xbscript.o ,bin\bc64\xbscript.exe,, lib\bc64\pp.a lib\bc64\common.a lib\bc64\debug.a lib\bc64\vm.a lib\bc64\rtl.a lib\bc64\pcrepos.a lib\bc64\gtwin.a lib\bc64\lang.a lib\bc64\rdd.a lib\bc64\macro.a lib\bc64\dbffpt.a lib\bc64\redbffpt.a
lib\bc64\dbfntx.a lib\bc64\dbfnsx.a lib\bc64\dbfcdx.a
lib\bc64\dbfmdx.a lib\bc64\bmdbfcdx.a lib\bc64\redbfcdx.a
lib\bc64\sixcdx.a lib\bc64\bmsixcdx.a lib\bc64\hbsix.a lib\bc64\hsx.a
lib\bc64\usrrdd.a lib\bc64\rdds.a lib\bc64\codepage.a lib\bc64\ct.a lib\bc64\zlib.a ws2_32.a cw64mt.a import64.a
Turbo Incremental Link64 6.98 Copyright (c) 1997-2023 Embarcadero Technologies, Inc.
Error: Unresolved external 'HB_FUN_DLLPREPARECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLUNLOAD' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_SETLASTERROR' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_GETPROCADDRESS' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLEXECUTECALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Error: Unresolved external 'HB_FUN_DLLCALL' referenced from E:\FW\XHARBOUR\OBJ\BC64\XBSCRIPT.O
Please try after: 2024-01-06 21:26 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
Perfect! Now I'm going to try again all the builds (MSC, BCC, MGW) with minimal batch and report back here.
With this batch:
SET CC_DIR=e:\fw\temp\bcc77
SET CFLAGS=-Wno-unknown-pragmas
make_bc all
I get this on the console:
E2075 Incorrect command line option: -Wno-unknown-pragmasFatal: Unable
to execute command: bcc32c
With this batch:
SET CC_DIR=e:\fw\temp\bcc77
SET CFLAGS=-w-
make_bc all
I get this on the console:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience bcc32c's bin directory was added to your PATH
Creating System Files (ST) ...
Wrote crash dump file "C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-a5c8af.dmp"
0x00CF4AA2 (0x00000002 0x00000000 0x0000000A 0x079F1548)
bcc32c.exe: error: clang frontend command failed due to signal (use
-Xdriver -v to see invocation)
Embarcadero Technologies Inc. bcc32c version 5.0.2
(f0862325.b014dc86.38289) (based on LLVM 5.0.2)
Target: i686-pc-windows-omf
Thread model: posix
InstalledDir: e:\FW\Temp\BCC77\bin
bcc32c.exe: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source,and associated run script.
bcc32c.exe: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at: bcc32c.exe: note: diagnostic msg: C:\Users\ENRICO~1\AppData\Local\Temp\dllcall-34f77d.c
Wrote crash dump file "C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-70bcdf.dmp"
0x0159C016 (0x03BDE8B0 0x03BDE91C 0x00000000 0x00000000)
0x03BDE810 (0x03BDE91C 0x00000000 0x00000000 0x00000000) <unknown module> 0x03BDE8B0 (0x03BFD740 0x03BFD9A8 0x03BFDA88 0x03BFDA50) <unknown module> 0x03BFDBA0 (0x00000000 0x03BFBF98 0x00000002 0x00000000) <unknown module> 0x03BFE1B0 (0x03BFBF98 0x00000002 0x00000000 0x00000001) <unknown module>
With this batch:
SET CC_DIR=e:\fw\temp\bcc77
SET CFLAGS=-w-
make_bc all
I get this on the console:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience bcc32c's bin directory was added to your PATH
Creating System Files (ST) ...
Wrote crash dump file "C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-a5c8af.dmp"
0x00CF4AA2 (0x00000002 0x00000000 0x0000000A 0x079F1548)
bcc32c.exe: error: clang frontend command failed due to signal (use
-Xdriver -v to see invocation)
I don't have bcc77 - I suggest 'bcc32c /?'. From the error you got it
clearly say -Wunknown-prgams so its a CLang and -W- is not applicable.
You may aalso try -Wno-pragmas.
Il 07/01/2024 10:05, Enrico Maria Giordano ha scritto:
With this batch:
SET CC_DIR=e:\fw\temp\bcc77
SET CFLAGS=-w-
make_bc all
I get this on the console:
For your convenience xHarbour's bin directory was added to your PATH.
For your convenience bcc32c's bin directory was added to your PATH
Creating System Files (ST) ...
Wrote crash dump file "C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-a5c8af.dmp"
0x00CF4AA2 (0x00000002 0x00000000 0x0000000A 0x079F1548)
bcc32c.exe: error: clang frontend command failed due to signal (use -Xdriver -v to see invocation)
The error line is this:
bcc32c -c -tWM -D__WIN32__ -D_HAVE_SQLITE_CONFIG_H -DHAVE_CONFIG_H -DHARBOUR_CONF -DOPENSSL_NO_DEPRECATED -DHB_VM_ALL -DHB_FM_DL_ALLOC -I"source\rtl\zlib" -I"contrib\pdflite\include" -I"contrib\png" -I"contrib\tiff" -I"contrib\jpeg" -I"include"
-I"e:\fw\temp\bcc77\include" -I"obj\b32c" -I"contrib\sixapi\include" -I"contrib\freeimage\include" -I"contrib\gd\include"
-I"contrib\xwt\include" -I"contrib\xwt\src\xwt_win" -O2 -q -a8 -w -w-
-a4 -oobj\b32c\dllcall.obj source\rtl\dllcall.c
If I replace bcc32c with bcc32 in this line it compiles fine.
Compiling contribs I get:
bcc32c -c -I"contrib\hbzlib\include" -I"include" -vi -R- -H- -O2 -q -a8 -w- -X- -oobj\b32c\ziparchive.obj contrib\hbzlib\ziparchive.cpp
Warning: option '-R-' is not supported in Clang-based compiler.
Warning: option '-H-' is not supported in Clang-based compiler.
I don't have bcc77 - I suggest 'bcc32c /?'.
From the error you got it clearly say -Wunknown-prgams so its a CLang
and -W- is not applicable. You may aalso try -Wno-pragmas.
Il 07/01/2024 17:13, Ron Pinkas ha scritto:
I don't have bcc77 - I suggest 'bcc32c /?'.
The help is identical to bcc32.exe. These are the files:
28/10/2023 19:04 1.600.416 bcc32.exe
28/10/2023 18:52 36.937.120 bcc32c.exe
From the error you got it clearly say -Wunknown-prgams so its a CLang
and -W- is not applicable. You may aalso try -Wno-pragmas.
Unfortunately, it does not accept any of the CLANG compiler switches.
But accept -w- (lowercase, just like bcc32.exe). The problem is the
error with dllcall.c. The other modules compile fine.
Sorry I misssed it - WHICH error with dllcall.c?
I don't have bcc77 - I suggest 'bcc32c /?'. From the error you got it
clearly say -Wunknown-prgams so its a CLang and -W- is not applicable.
You may aalso try -Wno-pragmas.
Compiling contribs I get:
bcc32c -c -I"contrib\hbzlib\include" -I"include" -vi -R- -H- -O2 -q
-a8 -w- -X- -oobj\b32c\ziparchive.obj contrib\hbzlib\ziparchive.cpp
Warning: option '-R-' is not supported in Clang-based compiler.
Warning: option '-H-' is not supported in Clang-based compiler.
Encrico,
I am not sure what -R intention was you may try -R wither older to see
what it was and evaluate if it is needed and if so set a different set
of flags based on compiler used.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 399 |
Nodes: | 16 (2 / 14) |
Uptime: | 66:49:02 |
Calls: | 8,355 |
Calls today: | 15 |
Files: | 13,159 |
Messages: | 5,894,218 |
Posted today: | 1 |