>Hi Viktor and Toninho
>Please check the location of c0d32.obj and if it's known for BCC
>compiler so it can locate during linking. AFAIR ilink in BCC needs
>valid paths set in ilink32.cfg. It was -L option or sth like that.
>You can also use bcc32.exe as wrapper to ilink32.exe and if I'm
>not wro
Hi Przemek,
Very good point. It may explain Toninho's problem
well. Since he was not using the central config files
(which is BTW an install time requirement for all
Borland C compilers), and he was only copying in
bcc32.cfg, ilink32 was clueless about lib dirs.
Thanks a lot. This also means thi
On Wed, 12 Nov 2008, Szak�ts Viktor wrote:
Hi Viktor and Toninho
>>> BTW, do you have a 'c0d32.obj' in your Borland lib dir?
>> Yes, I have.
> Very strange. No more ideas here. Anyone?
Please check the location of c0d32.obj and if it's known for BCC
compiler so it can locate during linking. AFAI
Hi Toninho,
Hi Viktor,
I did above changes, but I still need use HB_BUILD_DLL=no.
BTW, do you have a 'c0d32.obj' in your Borland lib dir?
Yes, I have.
Very strange. No more ideas here. Anyone?
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbo
>This shouldn't make a difference, at least in 5.5, but I've
>never tried that. I'd rather suggest to use C_USR to setup
>special Harbour flags '-5 -6'. '-WC' '-w-inl-' are surely
>unnecessary, and even '-a8' AFAIK. Then, the bcc32.cfg
>stored in your Borland C bin dir would only need -I and
>-L li
Hi Toninho,
[ I've just tested the default build using
BCC 5.8.2, and it finishes without error, just
as 5.5.1. ]
Maybe is related to my environment. I don´t have my bcc folders in
path. To compile Harbour, I copy bcc32.cfg to harbour folder and call
make_b32.bat
---bcc32.cfg---
-IE:\harbour\b
>As a workaround try disabling .dlls using:
>set HB_BUILD_DLL=no
Hi Viktor thanks. It works.
>[ I've just tested the default build using
>BCC 5.8.2, and it finishes without error, just
>as 5.5.1. ]
Maybe is related to my environment. I don´t have my bcc folders in
path. To compile Harbour, I copy
Hi Toninho,
This seems like an older problem exploited
by enabling .dll building by default.
As for the proper solution, it's difficult
to tell it without having this compiler
freely available.
As a workaround try disabling .dlls using:
set HB_BUILD_DLL=no
[ I've just tested the default build
