Home
last modified time | relevance | path

Searched refs:why (Results 1 – 17 of 17) sorted by relevance

/ndk/sources/host-tools/sed-4.2.1/sed/
Dsed.h190 void bad_prog P_((const char *why));
Dcompile.c204 bad_prog(why) in bad_prog() argument
205 const char *why; in bad_prog()
209 myname, cur_input.name, CAST(unsigned long)cur_input.line, why);
215 why);
/ndk/sources/host-tools/make-3.81/tests/scripts/features/
Ddouble_colon115 # TEST 8: I don't grok why this is different than the above, but it is...
/ndk/docs/text/
DIMPORT-MODULE.text32 (The reason why it must be at the end is to avoid messing with
223 docs/ANDROID-MK.html to understand why.
DSYSTEM-ISSUES.text94 error messages that make it difficult to know why a dynamic load/link
DCHANGES.text1896 to use the extensions why they have been probed with eglGetProcAddress() or
/ndk/sources/host-tools/make-3.81/glob/
DChangeLog87 found or not, we'll always return it, so why bother searching?
/ndk/sources/host-tools/make-3.81/
Dreadme.vms266 SYS$SYSROOT:[SYSLIB] (I don't remember why I didn't just use
Daclocal.m4648 # This was a mistake. There are at least two reasons why we must not
/ndk/build/tools/
DDEV-SCRIPTS-USAGE.TXT92 This directory contains platform-specific files. The reason why it
/ndk/sources/host-tools/make-3.81/doc/
Dmake.info-11626 `foo.c' includes it, and that that is why `defs.h' was added to
2237 for phony targets (*note Implicit Rules::). This is why declaring a
3423 is why Emacs' `compile' command passes the `-k' flag by default.
3463 if a signal happens. Some reasons why you might do this are that the
3490 but there are many things to know about how they work and why, and about
3917 You may be wondering why you would want to define a command string
4001 significance of `$' is why you must write `$$' to have the effect of a
4870 ignored, according to the condition. This is why the larger syntactic
6434 correct them all before the next attempt to compile. This is why Emacs'
Dmake.texi1886 that @file{foo.c} includes it, and that that is why @file{defs.h} was
2637 phony targets (@pxref{Implicit Rules}). This is why declaring a target
4101 is why Emacs' @code{compile} command passes the @samp{-k} flag by
4151 if a signal happens. Some reasons why you might do this are that the
4184 but there are many things to know about how they work and why, and about
4749 You may be wondering why you would want to define a command string that
4844 special significance of @samp{$} is why you must write @samp{$$} to have
5929 ignored, according to the condition. This is why the larger syntactic
7863 correct them all before the next attempt to compile. This is why Emacs'
/ndk/sources/host-tools/gdb-pretty-printers/stlport/gppfs-0.2/
DCOPYING675 <http://www.gnu.org/philosophy/why-not-lgpl.html>.
/ndk/sources/host-tools/sed-4.2.1/
DCOPYING675 <http://www.gnu.org/philosophy/why-not-lgpl.html>.
/ndk/sources/host-tools/ndk-stack/binutils/
DCOPYING3674 <http://www.gnu.org/philosophy/why-not-lgpl.html>.
/ndk/sources/host-tools/make-3.81/config/
Dtexinfo.tex1049 % FYI, plain.tex uses \\ as a temporary control sequence (why?), but
6283 % all be worked out, but why? Either we support ^^ or we don't.
6309 % character. What I don't understand is why it works in the *value*
/ndk/sources/host-tools/sed-4.2.1/build-aux/
Dtexinfo.tex1116 % FYI, plain.tex uses \\ as a temporary control sequence (why?), but
7453 % all be worked out, but why? Either we support ^^ or we don't.
7479 % character. What I don't understand is why it works in the *value*