Re: Any progress with FIS GT.M?
Luis,
I fixed the #!/bin/sh in the scripts. I checked our CVS history and email archives and found that the scripts are bourne shell
scripts. The gtmstart script had a colon on the first line which giggle searches showed as an indicator for the Bourne shell. I
will make sure that the next release has these scripts fixed.
Testing also turned up one more missing item in CMakeLists.txt. The GT.CM servers needed to use the gtmexe_symbsols.exports
while linking.
Please integrate at your convenience.
Thanks,
Amul
PS: Happy 4th!
On 07/02/12 10:54, Shah, Amul wrote:
> Luis,
> GT.M Regression Test Suite results are nearly complete. With the exception of a few configuration related issues and tests that need to be fixed, everything is in good shape.
>
> The first round of testing hit a latent GT.M bug that is fixed in the upcoming release. I back ported the change which switches memcpy to memmove in several modules. Because the sources have diverged a from the original V5.5-000 I modified sr_linux/release_name.h to change the reported version to V5.5-000A. I have pushed these changes to git hub. Please integrate at your convenience.
>
> thanks,
> Amul
>
> _____________
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
>
>
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Reply to: