Bug 872127 - Part 1: Remove support for MOZ_CUSTOM_STDINT_H; r=Waldo,ted

configure.in

@@ -1734,16 +1734,6 @@ case "$host" in
     ;;
 esac
 
-dnl Check for using a custom <stdint.h> implementation
-dnl ========================================================
-AC_MSG_CHECKING(for custom <stdint.h> implementation)
-if test "$MOZ_CUSTOM_STDINT_H"; then
-  AC_DEFINE_UNQUOTED(MOZ_CUSTOM_STDINT_H, "$MOZ_CUSTOM_STDINT_H")
-  AC_MSG_RESULT(using $MOZ_CUSTOM_STDINT_H)
-else
-  AC_MSG_RESULT(none specified)
-fi
-
 dnl Get mozilla version from central milestone file
 MOZILLA_VERSION=`$PERL $srcdir/config/milestone.pl -topsrcdir $srcdir`
 MOZILLA_UAVERSION=`$PERL $srcdir/config/milestone.pl -topsrcdir $srcdir -uaversion`

js/public/LegacyIntTypes.h

@@ -17,13 +17,12 @@
  *         Indeed, if you use this header and third-party code defining these
  *         types, *expect* to encounter either compile errors or link errors,
  *         depending how these types are used and on the order of inclusion.
- *         It is safest to use only the JSAPI <stdint.h>-style types,
- *         customizing those types using MOZ_CUSTOM_STDINT_H if necessary.
+ *         It is safest to use only the <stdint.h> types.
  */
 #ifndef js_LegacyIntTypes_h
 #define js_LegacyIntTypes_h
 
-#include "mozilla/StandardInteger.h"
+#include <stdint.h>
 
 #include "js-config.h"
 

js/src/configure.in

@@ -1356,16 +1356,6 @@ case "$host" in
     ;;
 esac
 
-dnl Check for using a custom <stdint.h> implementation
-dnl ========================================================
-AC_MSG_CHECKING(for custom <stdint.h> implementation)
-if test "$MOZ_CUSTOM_STDINT_H"; then
-  AC_DEFINE_UNQUOTED(MOZ_CUSTOM_STDINT_H, "$MOZ_CUSTOM_STDINT_H")
-  AC_MSG_RESULT(using $MOZ_CUSTOM_STDINT_H)
-else
-  AC_MSG_RESULT(none specified)
-fi
-
 MOZ_DOING_LTO(lto_is_enabled)
 
 dnl ========================================================