FWH / xHarbour.com Unresolved external symbol

Post Reply
User avatar
patdriscoll
Posts: 16
Joined: Tue May 19, 2009 7:28 pm

FWH / xHarbour.com Unresolved external symbol

Post by patdriscoll »

Hello All,

I have just installed the latest xHarbour (non Beta) release from xHarbour.com and FWH 12.05 and have the following message when I compile:

xLINK: error: Unresolved external symbol '_SendInput referenced from FiveHCM.lib(KEYBRD.obj)'.
xLINK: error: Unresolved external symbol '_GlobalMemoryStatusEx referenced from FiveHCM.lib(MEM.obj)'.
xLINK: error: Unresolved external symbol '__chkstk referenced from FiveHCM.lib(C5CNEW.obj)'.

NOTE: I have perfomed a clean build. Worls with my old (very old) version of FWH and xHB.

Can anyone please advise a solution?

Cheers,

Pat
Pat Driscoll
Australia
User avatar
patdriscoll
Posts: 16
Joined: Tue May 19, 2009 7:28 pm

Re: FWH / xHarbour.com Unresolved external symbol

Post by patdriscoll »

Thanks for your email Antonio.
Pat Driscoll
Australia
User avatar
Antonio Linares
Site Admin
Posts: 42595
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Has thanked: 38 times
Been thanked: 86 times
Contact:

Re: FWH / xHarbour.com Unresolved external symbol

Post by Antonio Linares »

regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
patdriscoll
Posts: 16
Joined: Tue May 19, 2009 7:28 pm

Re: FWH / xHarbour.com Unresolved external symbol

Post by patdriscoll »

Thank you Antonio.

I now only have one unresolved external:

xLINK: error: Unresolved external symbol '__chkstk referenced from FiveHCM.lib(C5CNEW.obj)'.

Cheers,

Pat.
Pat Driscoll
Australia
User avatar
Antonio Linares
Site Admin
Posts: 42595
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain
Has thanked: 38 times
Been thanked: 86 times
Contact:

Re: FWH / xHarbour.com Unresolved external symbol

Post by Antonio Linares »

Pat,

I just emailed a modified lib to you that does not require chkstk :-)

For general infomation: _chkstk is automatically invoked by the (Microsoft) C compiler when a C function uses too much (over 4 Kb) local C variables. In this case, the variables should be dinamically allocated using hb_xgrab() and freed later on with hb_xfree():

http://www.codeguru.com/cpp/v-s/debug/article.php/c19241/Adventures-with-chkstk.htm
regards, saludos

Antonio Linares
www.fivetechsoft.com
Post Reply