David J Taylor wrote: >> There is one other thing that needs to be considered. This is a 64-bit >> system> In that case it's possible that the code may need to be >> changed to deal with it properly. For example using the VS 2005 >> compiler I have found that it uses a 64-bit integer instead of 32-bit >> integer for time_t. This could affect the quality of the results, >> it's hard to say. > > The version I'm testing is the 32-bit version of Vista, albeit on a 64-bit > capable CPU. 64-bit can be a pain though for subtle errors, I appreciate. >
That's a problem. There are even more subtle issues when you run a 32-bit O/S on a 64-bit system. I don't think we can even try to support that since there are likely to be too many unknowns. It's a very nasty mix. > I didn't think that a 64-bit version of NTP was included in the Meinberg > distribution. When I looked briefly at the Windows port in: > ntp-4.2.4p4\ports\winnt\ntp.dsw I found that VS2005 needed to convert the > format of some of the files - so it looked as if it might be for an older > version of Visual Studio. I can't build NTP because the openssl > definitions appear to be missing from the download, and I got this error > as well: > With VS 2005, just open the dsw file and tell it to convert all the project files. I recently add the necessary macros to the dsp files so that I don't have to add a bunch of macros every time I pull in a new tarball. I'm only building on VS 2005 these days. Building on VS 6 I reserve for releasing builds. We don't ship the OpenSSL sources due to possible export regulations. You can download that yourself from the openssl.org site. Just follow the build instructions for Windows. I use the nt suboption. > BSCMAKE: error BK1506 : cannot open file '.\debug\nt_clockstuff.sbr': No > such file or directory > hard to say why but it obviously was not compiled. Danny > > > Comments? _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
