Technically, this isn't a compiler that we claim to support or test. The warnings you listed above should not be fatal though, and there's really no way for us to know what they mean since we can't tell which data type 776 and 264 refer to. These could be harmless reassigns, like a unsigned long to an unsigned int, or something that could cause a problem. Also, remember that our object code (.o and .lib files) are compiled in the current compatibility mode (Visual C++, Borland, etc). It could be that the mode you are in is not compatible for GCC. We don't have a specific mode for GCC, so I'm not sure which object code format it expects.
Best Regards,
Chris Matthews
Measurement Studio Support Manager