1. Cannot compile Cirrus Mail

I tried to compile Cirrus Mail (newest version) using
ecw -lcc but I get this error:

How is it?

.... (many files)
ump node tableOverflow in jump node tableOverflow in jump node tableOverflow in
jump node tableOverflow in jump node tableOverflow in jump node tableOverflow in
 jump node tableOverflow in jump node tableOverflow in jump node tableOverflow i
n jump node tableOverflow in jump node tableOverflow in jump node tableOverflow
in jump node tableOverflow in jump node tableOverflow in jump node tableOverflow
 in jump node tableOverflow in jump node tableOverflow in jump node tableOverflo
w in jump node tableOverflow in jump node tableOverflow in jump node tableOverfl
ow in jump node tablefind_1.c
accounts.c
login.c
login_0.c
clock.c
Error clock.c: 29  invalid use of `boolean'
Error clock.c: 30  missing name for parameter 3 to function `_41SetWindowRgn'
Error clock.c: 30  redeclaration of `_41SetWindowRgn' previously declared at
main_.h 5944
Error clock.c: 35  illegal expression
4 errors, 0 warnings
linking
cannot open clock.obj
you can now execute: cirrus.exe

new topic     » topic index » view message » categorize

2. Re: Cannot compile Cirrus Mail

Akusaya writes:
> I tried to compile Cirrus Mail (newest version) using
> ecw -lcc but I get this error:
> .... (many files)
> find_0.c
> Overflow in jump node table...
>
> clock.c
> Error clock.c: 29  invalid use of `boolean'

The Overflow is due to a failure in the Lcc C compiler.
It obviously has a hard-coded limit on its "jump node table".
I tried removing the "-O" option when compiling find_0.c,
but still got the messages. However it managed to produce a .obj file
in spite of these messages.

The error in clock.c arises because the author of Lcc has
hard-coded into his parser, an extra fundamental data type
(like int, char, double etc.) that he calls "_Bool". There is no
way to undefine or avoid this symbol. What you can do is
change the Euphoria program, to replace "Bool" by something
else in 2 places - I found "bool" was fine. 
Maybe the Translator can watch out for this symbol in the next release.

With these changes, the program translates, compiles and
runs using Lcc.

If you use Borland or Watcom, there are no errors or warnings,
and the program seems to run fine - although I can't say that I tested the
e-mail program thoroughly.

Jordah Ferguson writes:
> I found out it was nearly impossible to translated most win32lib apps. 

If you use Borland or Watcom you should rarely have a problem.
If you use Lcc, you will probably get an error message from 
at least one of the Win32Lib files. Simply remove the "-O" (optimize)
option in emake.bat for any files that give you an error.
I highly recommend that people use Borland or Watcom.
You'll have fewer problems, and you'll get faster code.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu