Hi,
There's a stray file, dlls/checklink.c, in Wine CVS with these contents:
int main(void) { return 0; }
It must be a leftover from a configure run. I suspected my own tree but but it came back after I removed it and did a cvs update.
-Hans
On Mon, Jan 12, 2004 at 09:12:54PM -0500, Hans Leidekker wrote:
Hi,
There's a stray file, dlls/checklink.c, in Wine CVS with these contents:
int main(void) { return 0; }
It must be a leftover from a configure run. I suspected my own tree but but it came back after I removed it and did a cvs update.
No, it belongs there. It is for missing symbol checking.
Ciao, Marcus
--- Hans Leidekker hans@it.vu.nl wrote:
It must be a leftover from a configure run. I suspected my own tree but but it came back after I removed it and did a cvs update.
I have seen it before and always thought it was supposed to be there. =)
Thanks Steven
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
No! it is there for a purpose. When doing winelib apps. The actual app is a shared library. Therefor the compiler will not warn about missing symbols since they can be resolved on load time by the running process. What the check-link stage does, is compile the winelib as an ELF executable. to see if it all links with out any missing symbols. One missing symbol will be "main". Hence the below file. It will automatically be linked by the check-link stage in the makefiles.
Free Life Boaz
Hans Leidekker wrote:
Hi,
There's a stray file, dlls/checklink.c, in Wine CVS with these contents:
int main(void) { return 0; }
It must be a leftover from a configure run. I suspected my own tree but but it came back after I removed it and did a cvs update.
-Hans
On Tuesday 13 January 2004 10:50, Boaz Harrosh wrote:
No! it is there for a purpose.
OK. Thanks all for educating me!
-Hans