instead of just going on as normal if __RENAME() is used in kernel

(_KERNEL) or standalone (_STANDALONE) files, replace it with some
text that'll cause an error.  __RENAME() should never be used in
the kernel (there's no need, at least, with the current way of doing
things), and is downright annoying in standalone code.  (In a standalone
build environment, there may be no sane way to do symbol renaming,
which means that even just faking it and defining it to emptyness
would cause problems if it were actually needed.)
This commit is contained in:
cgd 2000-02-03 02:20:13 +00:00
parent fefea44b6f
commit 63a0836e51
1 changed files with 5 additions and 1 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: cdefs.h,v 1.30 1999/12/13 08:25:16 itohy Exp $ */
/* $NetBSD: cdefs.h,v 1.31 2000/02/03 02:20:13 cgd Exp $ */
/*
* Copyright (c) 1991, 1993
@ -162,6 +162,7 @@
#endif /* NO_KERNEL_RCSIDS */
#endif /* _KERNEL */
#if !defined(_STANDALONE) && !defined(_KERNEL)
#ifdef __GNUC__
#define __RENAME(x) ___RENAME(x)
#else
@ -171,5 +172,8 @@
#error "No function renaming possible"
#endif /* __lint__ */
#endif /* __GNUC__ */
#else /* _STANDALONE || _KERNEL */
#define __RENAME(x) no renaming in kernel or standalone environment
#endif
#endif /* !_SYS_CDEFS_H_ */