GEustace@massey.ac.nz (Glen Eustace) (12/08/89)
I have been advised by the folks from Sun East that the current version
of the PC-NFS Toolkit will produce executables that work with MSC5. I
have not found that to be the case, in fact no socket based code I have
compiled with MSC5 has ever worked yet the same code compiled with MSC4
usually does.
I have checked all the libraries against the master disks, just in case
something somewhere has been corrupted. I actually did find a single
byte error in one of the MSC4 compact libraries, but I only use either
large or small so it should not matter.
This is what I have,
PC-NFS ToolKit v1.0, Part No. 740-1009-02 dated 9 Apr 87 1:00
MSC 4.0, no part no. master disks have datestamps 27 Jun 86 4:00
MSC 5.1, no part no. master disks have datestamps 7 Mar 88 5:10
LINK 3.65
I have tried different combinations of options on the compiler, re:
optimisation but it doesn't seem to make any difference, I always give an
/ST:16384 on the link as an example prog I got from Geoff Arnold had that
and I have found that without it even code compiled with MSC 4 fails to
work correctly.
I have tried different options on the link. For awhile I was using
/E/F/PAC but found that on LINK 3.61 that I often got corrupt executables
so I have stopped doing that.
If anyone is having success using MSC5 and the ToolKit, can you please
tell me how you do it, I find having to change compilers depending on
whether a program uses sockets to be annoying, I just get used to using
a routine in MSC5 then go to use it in MSC4 and it doesn't exist!
--
-----------------------------------------------------------------------
Glen Eustace, Software Manager, Computer Centre, Massey University,
Palmerston North, New Zealand. Phone: +64 63 69099 x7440 GMT+12
E-Mail via Internet: G.Eustace@massey.ac.nz
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>