From e4ad7a8080e4ac0b868fa7cf39bc5ad9a6e0bee1 Mon Sep 17 00:00:00 2001 From: Jeremy Huddleston Date: Sun, 10 Feb 2008 19:07:49 -0800 Subject: Fixed #ifdef checks that were using i386 to use __i386__ """ It's simply obsolete, sloppy, compiler namespace pollution. The compiler is not allowed to predefine symbols that might conflict with ordinary identifiers. For backwards compatibility gcc currently predefines i386 when compiling for x86 32-bit (but not 64-bit), but that will go away. It is also not defined if you specify -ansi when invoking the compiler, because then it is seriously standards compliant. Other compilers shouldn't define it either. Correct code shouldn't rely on it being defined. However __i386__ is safe and proper. """ --- Xos_r.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Xos_r.h') diff --git a/Xos_r.h b/Xos_r.h index f52bde7..7ce72ac 100644 --- a/Xos_r.h +++ b/Xos_r.h @@ -237,7 +237,7 @@ extern void XtProcessUnlock( #elif !defined(XTHREADS) && !defined(X_FORCE_USE_MTSAFE_API) /* Use regular, unsafe API. */ -# if defined(X_NOT_POSIX) && !defined(i386) && !defined(SYSV) +# if defined(X_NOT_POSIX) && !defined(__i386__) && !defined(SYSV) extern struct passwd *getpwuid(), *getpwnam(); # endif typedef int _Xgetpwparams; /* dummy */ -- cgit v1.2.3