ChangeLog: 2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>

[Ron Pinkas]

2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND

Reynaldo, this shouldd fix your BCC_LIB problem.

[Reynaldo Henrique]

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Ok, thank you,


Reynaldo Henrique

[Ron Pinkas]

Post by Reynaldo Henrique

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Ok, thank you,
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail.
www.avg.com

Please do NOT set BCC_LIB manally ;)

[Reynaldo Henrique]

Post by Ron Pinkas

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Please do NOT set BCC_LIB manally ;)

Thanks, but still give the same errors. I updated my xharbour sources
and it apears the sane errors.


Thanks,

Reynaldo Henrique

[Ron Pinkas]

Post by Reynaldo Henrique

Post by Ron Pinkas

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Please do NOT set BCC_LIB manally ;)

Thanks, but still give the same errors. I updated my xharbour sources
and it apears the sane errors.
Thanks,
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail.
www.avg.com

Mmm sorry, please show latest functios.log

[Reynaldo Henrique]

Post by Ron Pinkas

Post by Reynaldo Henrique

Post by Ron Pinkas

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Please do NOT set BCC_LIB manally ;)

Thanks, but still give the same errors. I updated my xharbour sources
and it apears the sane errors.
Thanks,
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail.
www.avg.com

Mmm sorry, please show latest functios.log

here you are:

*** START [C:\xharbour\make_bc.bat](all)
*** started [C:\xharbour\winmake\find_bc.bat]
*** started(bcc32) [C:\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:\xharbour\winmake\found_cc.bat]
*** finished[0] [C:\xharbour\winmake\find_bc.bat]
*** END [C:\xharbour\make_bc.bat]

thanks,


Reynaldo Henrique

[Ron Pinkas]

Post by Reynaldo Henrique

Post by Ron Pinkas

Post by Reynaldo Henrique

Post by Ron Pinkas

Post by Ron Pinkas
2024-01-06 16:46 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* winmake/find_bc.bat
Moved BCC_LIB generation to :FOUND
Reynaldo, this shouldd fix your BCC_LIB problem.

Please do NOT set BCC_LIB manally ;)

Thanks, but still give the same errors. I updated my xharbour sources
and it apears the sane errors.
Thanks,
Reynaldo Henrique
--
O software antivírus AVG realizou uma checagem de vírus neste e-mail.
www.avg.com

Mmm sorry, please show latest functios.log

*** START [C:\xharbour\make_bc.bat](all)
*** started [C:\xharbour\winmake\find_bc.bat]
*** started(bcc32) [C:\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:\xharbour\winmake\found_cc.bat]
*** finished[0] [C:\xharbour\winmake\find_bc.bat]
*** END [C:\xharbour\make_bc.bat]
thanks,
Reynaldo Henrique

Pleaae show log again, after: 2024-01-06 21:26 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>

[Reynaldo Henrique]

Post by Ron Pinkas

Post by Reynaldo Henrique

Post by Ron Pinkas
Mmm sorry, please show latest functios.log

*** START [C:\xharbour\make_bc.bat](all)
*** started [C:\xharbour\winmake\find_bc.bat]
*** started(bcc32) [C:\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:\xharbour\winmake\found_cc.bat]
*** finished[0] [C:\xharbour\winmake\find_bc.bat]
*** END [C:\xharbour\make_bc.bat]
thanks,
Reynaldo Henrique

Pleaae show log again, after: 2024-01-06 21:26 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>

Ron, Now it is working fine. I build xHarbour fine.


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]
EXIT BCC_LIB: c:\borland\bcc770\lib
*** finished[0] [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** END[0] [C:\Users\rhfsy\xharbour\make_bc.bat]

Thanks,

Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique
Ron, Now it is working fine. I build xHarbour fine.

Can you build with bcc32c.exe successfully? If yes, can I see your
bcc32c.cfg and the exact commands are you using?

[Reynaldo Henrique]

Post by Enrico Maria Giordano

Post by Reynaldo Henrique
Ron, Now it is working fine. I build xHarbour fine.

Can you build with bcc32c.exe successfully? If yes, can I see your
bcc32c.cfg and the exact commands are you using?

Enrico, I can build xHarbour with bcc32c (CLANG) 7.73 without any problem.

Here Is the bcc32c.cfg: working on bcc102\bin:

-isystem @\..\include\dinkumware64
-isystem @\..\include\windows\crtl
-isystem @\..\include\windows\sdk
-L@\..\lib\win32c\debug
-L@\..\lib\win32c\release
-L@\..\lib\win32c\release\psdk
-Xdriver -Qunused-arguments

Pay attention, it is not the bcc32c 7.70 (CLANG), I am using the bcc32c 7.73

Thanks,

Reynaldo Henrique

[Enrico Maria Giordano]

Post by Reynaldo Henrique

Post by Enrico Maria Giordano
Can you build with bcc32c.exe successfully? If yes, can I see your
bcc32c.cfg and the exact commands are you using?

Enrico, I can build xHarbour with bcc32c (CLANG) 7.73 without any problem.

Why are you using BCC64 include files for BCC32 compiler? Should not you
use dinkumware directory (without "64")?
Are you sure that @ is supported for the -L compiler switch? Please, try
to remove the above 3 lines and build xHarbour again.

Post by Reynaldo Henrique
-Xdriver -Qunused-arguments

What are they for?

Post by Reynaldo Henrique
Pay attention, it is not the bcc32c 7.70 (CLANG), I am using the bcc32c 7.73

Ok, noted. :-)

[Enrico Maria Giordano]

Post by Enrico Maria Giordano
Why are you using BCC64 include files for BCC32 compiler? Should not you
use dinkumware directory (without "64")?

You are right! Using dinkumware64 I could build all the contribs without
problems!

Now, only the calldll.c problem remains...

Anyway, I don't like bcc32c very much, it does not look like a finished
product yet.

[Ron Pinkas]

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano
Why are you using BCC64 include files for BCC32 compiler? Should not you
use dinkumware directory (without "64")?

You are right! Using dinkumware64 I could build all the contribs without
problems!
Now, only the calldll.c problem remains...
Anyway, I don't like bcc32c very much, it does not look like a finished
product yet.
--
Enrico Maria Giordano
http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

My strong recommendation is to never edit .crg fikes. Let the official installer install and create correct settings.

[Enrico Maria Giordano]

Post by Enrico Maria Giordano
Now, only the calldll.c problem remains...

I manage to compile it commenting out this line:

#include "hbapiitm.h"

Does it make sense?

[Enrico Maria Giordano]

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano
Now, only the calldll.c problem remains...

#include "hbapiitm.h"
Does it make sense?

No, probably not. I think doing so I have excluded all the rest of the
code, I don't know why exactly. :-(

[Ron Pinkas]

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano
Now, only the calldll.c problem remains...

#include "hbapiitm.h"
Does it make sense?

No, probably not. I think doing so I have excluded all the rest of the
code, I don't know why exactly. :-(

Just add -DNODLL to BOTH C and Harbour commands.

[Enrico Maria Giordano]

Post by Ron Pinkas

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano
Does it make sense?

No, probably not. I think doing so I have excluded all the rest of the
code, I don't know why exactly. :-(

Just add -DNODLL to BOTH C and Harbour commands.

I don't want to exclude calldll.c module. I have excluded it by mistake.
Anyway, I prepare a reduced sample that produces the error if compiled
with bcc32c.exe:

typedef union
{
double Double;
} RESULT;


int main()
{
RESULT Res;

asm volatile ( "" : "=r" ( Res ) );

return 0;
}

Can you try it and let me know if you get the same error?

Embarcadero C++ 7.70 for Win32 Copyright (c) 2012-2023 Embarcadero
Technologies, Inc.
dllcall.c:
fatal error: error in backend: Access past stack top!
bcc32c.exe: error: clang frontend command failed with exit code 70 (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.
dllcall.c:
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-4a8cec.c
Wrote crash dump file
"C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-0966b3.dmp"
0x00000000 (0x02FEE794 0x01A7D690 0x00000001 0x00000000) <unknown module>
0x00AAC019 (0x00007FFF 0x00000000 0x00010100 0x13D10C00)
0x0190623D (0x00000000 0x00010100 0x13D10C00 0x022A0A70)

[Enrico Maria Giordano]

Post by Enrico Maria Giordano
Anyway, I prepare a reduced sample

I PREPARED... :-)

[Ron Pinkas]

Post by Enrico Maria Giordano

Post by Ron Pinkas

Post by Enrico Maria Giordano

Post by Enrico Maria Giordano
Does it make sense?

No, probably not. I think doing so I have excluded all the rest of the
code, I don't know why exactly. :-(

Just add -DNODLL to BOTH C and Harbour commands.

I don't want to exclude calldll.c module. I have excluded it by mistake.
Anyway, I prepare a reduced sample that produces the error if compiled
typedef union
{
double Double;
} RESULT;
int main()
{
RESULT Res;
asm volatile ( "" : "=r" ( Res ) );
return 0;
}
Can you try it and let me know if you get the same error?
Embarcadero C++ 7.70 for Win32 Copyright (c) 2012-2023 Embarcadero
Technologies, Inc.
fatal error: error in backend: Access past stack top!
bcc32c.exe: error: clang frontend command failed with exit code 70 (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.
********************
C:\Users\ENRICO~1\AppData\Local\Temp\dllcall-4a8cec.c
Wrote crash dump file
"C:\Users\ENRICO~1\AppData\Local\Temp\bcc32c.exe-0966b3.dmp"
0x00000000 (0x02FEE794 0x01A7D690 0x00000001 0x00000000) <unknown module>
0x00AAC019 (0x00007FFF 0x00000000 0x00010100 0x13D10C00)
0x0190623D (0x00000000 0x00010100 0x13D10C00 0x022A0A70)

Enrico,

dllcall.c is a very low level file that must be adjusted to each new
compiler. It is offering a very specialized and complex feature that
allows calling dll functions without static declaraion. AFAIR we don't
need this feature, f.e. 64bit builds do not have it. In order to
support it we need someone with tthis specialized knowledge to address
it.

Ron

[Enrico Maria Giordano]

Post by Ron Pinkas
dllcall.c is a very low level file that must be adjusted to each new
compiler. It is offering a very specialized and complex feature that
allows calling dll functions without static declaraion. AFAIR we don't
need this feature, f.e. 64bit builds do not have it. In order to
support it we need someone with tthis specialized knowledge to address
it.

Ok, I will try to disable it then. Anyway, the problem with bcc32c.exe
is not related with dllcall.c. It looks like a bug in the compiler.

[Enrico Maria Giordano]

Post by Ron Pinkas
dllcall.c is a very low level file that must be adjusted to each new
compiler. It is offering a very specialized and complex feature that
allows calling dll functions without static declaraion. AFAIR we don't
need this feature, f.e. 64bit builds do not have it. In order to
support it we need someone with tthis specialized knowledge to address
it.

To be clear, are you proposing to disable dllcall.c for every compiler
or just for bcc32c.exe, other than 64 bit compilers?

[Enrico Maria Giordano]

One final (I hope) thing: I can build xHarbour for bcc32c.exe now, but I
had to add to my batch this:

SET CFLAGS=-w-

It's ok or it is better to add -w- to makefile.bc?

[Ron Pinkas]

Post by Enrico Maria Giordano
One final (I hope) thing: I can build xHarbour for bcc32c.exe now, but I
SET CFLAGS=-w-
It's ok or it is better to add -w- to makefile.bc?

Adding -w- to makefile.bc is ok, nut I prefer we keep seeing warnings.
Warnings do not break compilattion and may provide important info.

FWIW, I have been building all with bcc32c.exe of the FREE 7.30 for a
while - using make_bc.bat without any additional settings.

[Enrico Maria Giordano]

Post by Ron Pinkas

Post by Enrico Maria Giordano
One final (I hope) thing: I can build xHarbour for bcc32c.exe now, but I
SET CFLAGS=-w-
It's ok or it is better to add -w- to makefile.bc?

Adding -w- to makefile.bc is ok, nut I prefer we keep seeing warnings.
Warnings do not break compilattion and may provide important info.

Ok, I keep -w- in my batch and leave makefile.bc untouched.

[Ron Pinkas]

Post by Enrico Maria Giordano

Post by Ron Pinkas
dllcall.c is a very low level file that must be adjusted to each new
compiler. It is offering a very specialized and complex feature that
allows calling dll functions without static declaraion. AFAIR we don't
need this feature, f.e. 64bit builds do not have it. In order to
support it we need someone with tthis specialized knowledge to address
it.

To be clear, are you proposing to disable dllcall.c for every compiler
or just for bcc32c.exe, other than 64 bit compilers?

Disable only for compilers that can't compile it. :)

[Enrico Maria Giordano]

Post by Ron Pinkas

Post by Enrico Maria Giordano
To be clear, are you proposing to disable dllcall.c for every compiler
or just for bcc32c.exe, other than 64 bit compilers?

Disable only for compilers that can't compile it. :)

OK

[Reynaldo Henrique]

Ron,

Post by Reynaldo Henrique

Post by Ron Pinkas
Pleaae show log again, after: 2024-01-06 21:26 UTC-0500 Ron Pinkas
<ronpinkas/AT/gmail/com>

Ron, Now it is working fine. I build xHarbour fine.
*** 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]
EXIT BCC_LIB: c:\borland\bcc770\lib
   *** finished[0] [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** END[0] [C:\Users\rhfsy\xharbour\make_bc.bat]

I mean It still haveing the same errors:

here is the functions.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= )
+++ 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]
EXIT BCC_LIB:
"c:\borland\bcc770\lib\win32\release";"c:\borland\bcc770\lib\win32\release\psdk"

*** finished[0] [C:\Users\rhfsy\xharbour\winmake\find_bc.bat]
*** END[0] [C:\Users\rhfsy\xharbour\make_bc.bat]

Thanks,

Reynaldo Henrique