From be9d87ad962b0216d0ff92be75d90e3b36eeadb9 Mon Sep 17 00:00:00 2001
From: Aaron Crane <arc@cpan.org>
Date: Fri, 13 Oct 2017 15:14:20 +0200
Subject: Don't try to use <values.h>

All the information it contains can be gleaned more readily from C89
<limits.h> and <float.h>.
---
 config_h.SH | 8 --------
 1 file changed, 8 deletions(-)

(limited to 'config_h.SH')

diff --git a/config_h.SH b/config_h.SH
index ca35bad96a..b1b9c8c6c9 100755
--- a/config_h.SH
+++ b/config_h.SH
@@ -793,14 +793,6 @@ sed <<!GROK!THIS! >$CONFIG_H -e 's!^#undef\(.*/\)\*!/\*#define\1 \*!' -e 's!^#un
  */
 #$i_utime I_UTIME		/**/
 
-/* I_VALUES:
- *	This symbol, if defined, indicates to the C program that it should
- *	include <values.h> to get definition of symbols like MINFLOAT or
- *	MAXLONG, i.e. machine dependant limitations.  Probably, you
- *	should use <limits.h> instead, if it is available.
- */
-#$i_values I_VALUES		/**/
-
 /* I_VFORK:
  *	This symbol, if defined, indicates to the C program that it should
  *	include vfork.h.
-- 
cgit v1.2.1