How to build Harbour 32 & 64 bits

[Enrico Maria Giordano]

A better solution would be to use BCC 7.30 for 64 bit:

http://xharbour.org/index.asp?page=down ... quired_win

[Joaquim Ferrer]

A partir del ultimo commit de harbour
2023-11-22 09:06 UTC+0100 Przemyslaw Czerpak (druzus/at/poczta.onet.pl)
He intentado construir harbour con BCC77 y da el siguiente error

Code: Select all  Expand view

bcc32.exe   -I. -I../../../../../../include -q -tWM -CP437 -w-sig- -w-aus- -w-ccc- -w-csu- -w-par- -w-rch- -w-ucp- -w-use- -w-prc- -w-pia- -d -O2 -OS -Ov -Oc -Oi -6  -DUNICODE -DZIP_SUPPORT -Ic:/hbcore/src/3rd/zlib -I"c:\borland\bcc77\bin\..\Include" -I"c:\borland\bcc77\bin\..\Include\windows\crtl" -I"c:\borland\bcc77\bin\..\Include\windows\sdk"  -odirread.obj  -c ../../../dirread.c
../../../dirread.c:
Warning W8072 ../../../dirread.c 6072: Suspicious pointer arithmetic in function TIFFFetchNormalTag
Warning W8072 ../../../dirread.c 6608: Suspicious pointer arithmetic in function TIFFFetchNormalTag
Warning W8072 ../../../dirread.c 6615: Suspicious pointer arithmetic in function TIFFFetchNormalTag
Warning W8072 ../../../dirread.c 6890: Suspicious pointer arithmetic in function TIFFFetchNormalTag
Warning W8072 ../../../dirread.c 6896: Suspicious pointer arithmetic in function TIFFFetchNormalTag
Warning W8072 ../../../dirread.c 7620: Suspicious pointer arithmetic in function _TIFFPartialReadStripArray
Warning W8072 ../../../dirread.c 7630: Suspicious pointer arithmetic in function _TIFFPartialReadStripArray
Warning W8072 ../../../dirread.c 7640: Suspicious pointer arithmetic in function _TIFFPartialReadStripArray
Warning W8072 ../../../dirread.c 7651: Suspicious pointer arithmetic in function _TIFFPartialReadStripArray
*** 1 errors in Compile ***
../../../../../../config/rules.mk:88: recipe for target 'dirread.obj' failed
win-make[4]: *** [dirread.obj] Error 2
../../../config/lib.mk:68: recipe for target 'descend' failed
win-make[3]: *** [descend] Error 2
../../config/dir.mk:68: recipe for target 'tiff.inst' failed
win-make[2]: *** [tiff.inst] Error 2
../config/dir.mk:68: recipe for target '3rd.inst' failed
win-make[1]: *** [3rd.inst] Error 2
config/dir.mk:68: recipe for target 'src.inst' failed
win-make: *** [src.inst] Error 2
 

Parece ser que las mejoras introducidas en el commit de Phil Krylov el 2023-11-11 18:15:02
son los que rompen la compilación
Si regreso al commit anterior al 11-11-23, todo funciona ok

Mencionar que la compilación con mingw32 de la version actual de harbour, commit 22-11-23 funciona perfectamente

Alguien se ha encontrado con esto ?

Saludos

[Enrico Maria Giordano]

They are warnings, not errors. Can I see the batch you are using to build Harbour, so I can test it here?

[Joaquim Ferrer]

Here you are

Code: Select all  Expand view

PATH=%PATH%;c:\borland\bcc77\bin;c:\borland\bcc77\include
set compiler=bcc
set HB_WITH_OPENSSL=C:\hbcore\addons\OpenSSL-Win32\include
set HB_WITH_CURL=C:\hbcore\addons\curl\include\
set HB_DIR_NSIS=%ProgramFiles(x86)%\NSIS\
set HB_BUILD_PKG=yes
win-make clean install
 

Regards

[Enrico Maria Giordano]

I confirm the warnings. I fix them in my local copy but now there are others in zutil.h. You can ignore them with

Code: Select all  Expand view

win-make clean install HB_USER_CFLAGS="-w- -w!-"

Or wait for the Harbour developer to fix them. I already have a pull request pending but they seems not to be interested.

[Enrico Maria Giordano]

I confirm the warnings. I fix them in my local copy

If you want the fixed dirread.c just write me an email.

[Joaquim Ferrer]

Or wait for the Harbour developer to fix them. I already have a pull request pending but they seems not to be interested.

Are we running out of support for the Borland compiler?

[Enrico Maria Giordano]

If you want the fixed dirread.c just write me an email.

Sent to your private email.

[Enrico Maria Giordano]

Or wait for the Harbour developer to fix them. I already have a pull request pending but they seems not to be interested.

Are we running out of support for the Borland compiler?

For what I'm seeing it looks like we are running out of support for Harbour...