comparison src/s/linux.h @ 108:360340f9fd5f r20-1b6

Import from CVS: tag r20-1b6
author cvs
date Mon, 13 Aug 2007 09:18:39 +0200
parents 131b0175ea99
children 9f59509498e1
comparison
equal deleted inserted replaced
107:523141596bda 108:360340f9fd5f
234 #define HAVE_XRMSETDATABASE 234 #define HAVE_XRMSETDATABASE
235 #endif 235 #endif
236 236
237 /* XEmacs addition: */ 237 /* XEmacs addition: */
238 /* Linux defines these in <values.h>, but they can't be used in #if's 238 /* Linux defines these in <values.h>, but they can't be used in #if's
239 Include values.h now so that we don't get complaints if it's included later. */ 239 Include values.h now so that we don't get complaints if it's included
240 later. This loses with glibc-2 (libc-6) */
241
242 /* # include <features.h> */
243 #if 0
244 #if !(defined (__GLIBC__) && (__GLIBC__ >= 2))
240 245
241 #include <values.h> 246 #include <values.h>
242 #undef SHORTBITS 247 #undef SHORTBITS
243 #undef INTBITS 248 #undef INTBITS
244 #undef LONGBITS 249 #undef LONGBITS
245 250
251 #endif
252 #endif
246 /* The regex.o routines are a part of the GNU C-library used with Linux. */ 253 /* The regex.o routines are a part of the GNU C-library used with Linux. */
247 /* However, sometimes they disagree with the src/regex.h that comes with Emacs, 254 /* However, sometimes they disagree with the src/regex.h that comes with Emacs,
248 and that can make trouble in etags.c because it gets the regex.h from Emacs 255 and that can make trouble in etags.c because it gets the regex.h from Emacs
249 and the function definitions in libc. So turn this off. */ 256 and the function definitions in libc. So turn this off. */
250 /* XEmacs: in any case, Mule uses different regex routines. */ 257 /* XEmacs: in any case, Mule uses different regex routines. */