Searched refs:compiler (Results 1 – 4 of 4) sorted by relevance
| /libev/ |
| H A D | aclocal.m4 | 250 _LT_CC_BASENAME([$compiler])
927 _LT_TAGDECL([CC], [compiler], [1], [A language specific compiler])dnl
928 _LT_TAGDECL([with_gcc], [GCC], [0], [Is the compiler the GNU compiler?])dnl
937 compiler=$CC
4386 # NAG Fortran compiler
5929 compiler=$CC
7255 compiler=$CC
7387 compiler=$CC
7486 compiler=$CC
7553 compiler=$CC
[all …]
|
| H A D | configure | 1410 --with-gnu-ld assume the C compiler uses GNU ld [default=no]
1412 (or the compiler's sysroot if not specified).
5916 compiler=$CC
5921 $as_echo_n "checking command to parse $NM output from $compiler object... " >&6; }
7731 for cc_temp in $compiler""; do
7939 if test -n "$compiler"; then
7952 $as_echo_n "checking if $compiler supports -fno-rtti -fno-exceptions... " >&6; }
8314 $as_echo_n "checking for $compiler option to produce PIC... " >&6; }
8436 $as_echo_n "checking if $compiler supports -c -o file.$ac_objext... " >&6; }
8491 $as_echo_n "checking if $compiler supports -c -o file.$ac_objext... " >&6; }
[all …]
|
| H A D | ev.pod | 3985 is compiled with a C++ compiler or your C and C++ environments allow
4070 the C callback that libev requires. If your compiler can inline your
4378 compiler (at least, that's a stated goal, and breakage will be treated
4742 When optimising for size, use of compiler flags such as C<-Os> with
4810 This option only works when libev is compiled with a C compiler, as C++
5043 Depending on your compiler and compiler settings, you might get no or a
5047 However, these are unavoidable for many reasons. For one, each compiler
5050 targeting a specific compiler and compiler-version.
5052 Another reason is that some compiler warnings require elaborate
5056 And of course, some compiler warnings are just plain stupid, or simply
[all …]
|
| H A D | Changes | 208 - work around an apparent gentoo compiler bug.
357 with their C compiler.
|