MySQL Bugs: #8244: InnoDB compile failure on Tru64

Bug #8244	InnoDB compile failure on Tru64
Submitted:	1 Feb 2005 18:19	Modified:	1 Feb 2005 22:40
Reporter:	Lenz Grimmer	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	5.0.3-pre	OS:	Other (Tru64)
Assigned to:	Marko Mäkelä	CPU Architecture:	Any

Description:
The last 5.0.3 compile run failed on Tru64 with the following error:

03754: cc -DHAVE_CONFIG_H -I. -I. -I.. -I./../include -I./../../include -I../../include    -g  -DDBUG_ON -DSAFE_MUTEX -g -DDBUG_ON -DSAFE_MUTEX -O4 -pthread -ansi_alias -ansi_args -fast -inline speed -speculate all -DUNDEF_HAVE_GETHOSTBYNAME_R -DSNPRINTF_RETURN_TRUNC  -DUNIV_MUST_NOT_INLINE -c rem0rec.c
03755: cc: Info: File not optimized; use -g3 if both optimization and debug wanted. (suppressoptlvl)
03756: cc: Error: ./../include/rem0rec.ic, line 282: The compiler was expecting a ")", but one was not found.  This condition could have occured because "int16_t" is used in what might be a type cast, but there is no declared type of that name visible. (undefinedtype)
03757: 		ut_ad((int16_t)field_value
03758: ----------------^
03759: gmake[4]: *** [rem0rec.o] Error 1
03760: gmake[4]: Leaving directory `/local/users/mysqldev/barney/mysql-5.0.3-alpha/innobase/rem'

How to repeat:
Compile on Tru64 and observe the failure

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

I should have fixed this when you reported the Tru64 compilation error last time. It was also about int16_t. This one was not noticed by the compiler then, because ut_ad() assertions were not enabled in debug builds.