From: David E. <de...@us...> - 2007-01-04 19:55:54
|
Vince Coen wrote: > David Essex wrote: > ... >> I'm not sure what mean. > > I mean to link all the program elements / routines / > sub programs etc together with all runtime libraries > to make a complete running program that can be > transferred to any linux system and run as a standalone program. I think you mean a completly statically linked program. Yes you can do that, but it is generally not done (on UN*X) except by some system utilities. The only dependencies used by TC programs are TC-RTL, BDB and (n/pd)curses. UN*X: Except for the TC RTL, all other dependencies including BDB and (n)curses, are usually part of the UN*X (Linux/BSD) distribution Distributing binaries on UN*X (especially Linux) can be problematic. But this is not specific to TC, but a very common problem. Win32: The best approach is to create a TC-RTL DLL which includes BDB and PDcurses. Then all TC dependencies are resolved by the TC-RTL DLL. Down side, 3 different licenses in one DLL. On UN*X, you can check the dependencies using the LDD command. > ... > I am still not able to run all tests without some failures > despite using various versions of gcc including 4.1.1 , 3.3.6 > amd 2.96. > What is the corrent one to use? Version 0.63 should compile and run on 32-bit systems using GCC 2.x - 3.x. I have no information about 32-bit (or 64-bit) systems using GCC 4.x. I think the problem you have encountered is related to 64-bit systems. Since I have no experience with 64-bit systems, I really can't help. David Essex |