This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Mon, Feb 22, 2016 at 02:09:48PM +0100, Andreas Schwab wrote: > Dmitry V. Levin writes: > > On Mon, Feb 22, 2016 at 01:51:02PM +0100, Andreas Schwab wrote: > >> > >> > We certainly do have some macros defined directly in this file: > >> > $ grep '#define' config.h.in > >> > #define HAVE_IFUNC 0 > >> > #define HAVE_STRERROR 1 > >> > #define HAVE_REGEX 1 > >> > #define ARM_PCREL_MOVW_OK 0 > >> > #define HAVE_PT_CHOWN 0 > >> > #define HAVE_BUILTIN_TRAP 0 > >> > #define HAVE_PPC_FCFID 0 > >> > #define HAVE_PPC_FCTIDZ 0 > >> > >> Most of these (those defined to 0) are the templates used by AC_DEFINE. > > > > OK, so what's the preferred way of adding new macros > > like HAVE_BUILTIN_EXPECT and HAVE_REGEX? > > For case like HAVE_BUILTIN_EXPECT there is not much point in using > AC_DEFINE. Is PATCH v2 OK then? -- ldv
Attachment:
pgp2Y3Uf6Cm_K.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |