pike.git / src / configure.in

version» Context lines:

pike.git/src/configure.in:1444:   AC_ARG_WITH(checker, MY_DESCR([--with-checker],    [add extra memory checking overhead (Purify)]))   AC_ARG_WITH(gcov, MY_DESCR([--with-gcov],    [compile with support for gcov (gcc-only)]))   MY_AC_ARG_WITH(profiling, MY_DESCR([--with-profiling],    [add code used to profile pike code]),    [AC_DEFINE(PROFILING)])   MY_AC_ARG_WITH(internal-profiling, MY_DESCR([--with-internal-profiling],    [add profiling code for various internal things]),    [AC_DEFINE(INTERNAL_PROFILING)]) + MY_AC_ARG_WITH(mc-stack-frames, MY_DESCR([--with-mc-stack-frames], +  [add machine code to generate proper stack frames (X86-64 only)]), +  [AC_DEFINE(MACHINE_CODE_STACK_FRAMES)])   MY_AC_ARG_WITH(pg, MY_DESCR([--with-pg],[use the gcc -pg option]),    [PROFIL=-pg])   AC_ARG_WITH(poll, MY_DESCR([--with-poll], [use poll instead of select]), [], [    # Neither --with-poll nor --without-poll was specified    case "$pike_cv_sys_os" in    Solaris|HP-UX|OSF1|IRIX|Linux|UnixWare|OpenUNIX)   # PIKE_MSG_WARN([Defaulting to --with-poll since the OS is $pike_cv_sys_os.])   # Nothing to warn about, really...   # NOTE: Darwin (OSX/iOS) have poll, but it's layered on kqueue, so there's no   # real benefit to supporting it separately there.