| /netbsd/src/external/gpl3/gcc/dist/gcc/doc/ |
| D | headerdirs.texi | 8 @code{GCC_INCLUDE_DIR} means the same thing for native and cross. It is
10 stores the fixed include files. A cross compiled GCC runs
12 (If the cross compilation header files need to be fixed, they must be
13 installed before GCC is built. If the cross compilation header files
16 @code{GPLUSPLUS_INCLUDE_DIR} means the same thing for native and cross. It
25 @code{CROSS_INCLUDE_DIR} is used only by cross compilers. GCC
28 @code{TOOL_INCLUDE_DIR} is used for both native and cross compilers. It
30 use. For a cross-compiler, this is the equivalent of
31 @file{/usr/include}. When you build a cross-compiler,
|
| D | configterms.texi | 28 this is called a @dfn{cross}. If build, host, and target are all
32 is different, you are using a cross-compiler to build a native for a
34 @dfn{crossed native}, or @dfn{cross-built native}. If build and target
35 are the same, but host is different, you are using a cross compiler to
36 build a cross compiler that produces code for the machine you're
42 are different, you must have already built and installed a cross
|
| /netbsd/src/external/bsd/ntp/dist/sntp/m4/ |
| D | ntp_problemtests.m4 | 12 $host) cross=0 ;;
13 *) cross=1 ;;
30 case "$ntp_ept:$cross:$host" in
45 case "$ntp_ept:$cross:$host" in
59 case "$ntp_ept:$cross:$host" in
|
| D | sntp_problemtests.m4 | 12 $host) cross=0 ;;
13 *) cross=1 ;;
30 case "$sntp_ept:$cross:$host" in
39 case "$sntp_ept:$cross:$host" in
|
| D | ntp_crosscompile.m4 | 4 # Expose a cross-compilation indicator to makefiles
|
| D | ntp_prog_cc.m4 | 14 dnl we need to check for cross compile tools for vxWorks here
|
| /netbsd/src/tools/gdb/ |
| D | README.mknative | 3 This file describes how to use the cross-compiler to generate the
11 bootstrapping on a cross or native host. This is important: even on a
16 cross-generated. Though a $MACHINE_ARCH all uses the same config files, you
23 2. Build and install a cross toolchain (via "build.sh -U -m MACHINE tools").
32 cross toolchain (--build reflects the host platform, but --host and
34 native-to-NetBSD GDB on a cross host, and mknative pulls glue data
|
| /netbsd/src/games/battlestar/ |
| D | fly.c | 53 static char cross = 0; variable
142 if (cross) { in visual()
143 cross = 0; in visual()
146 cross = 1; in visual()
276 if (cross) in moveenemy()
|
| /netbsd/src/tools/gcc/ |
| D | README.mknative | 5 files may be generated on a cross-compile host without problems.
12 bootstrapping on a cross or native host. This is important: even on a
17 cross-generated. Though a $MACHINE_ARCH all uses the same config files, you
27 2. Build and install a cross toolchain (via "build.sh -m MACHINE tools").
75 cross toolchain (--build reflects the host platform, but --host and
77 native-to-NetBSD compiler on a cross host, and mknative pulls glue data
|
| /netbsd/src/external/gpl3/binutils/dist/config/ |
| D | acinclude.m4 | 6 dnl We are probably using a cross compiler, which will not be able to fully
8 dnl Find a working G++ cross compiler. This only works for the GNU C++ compiler.
43 dnl to get a correct fully linked executable with a cross compiler. For
44 dnl most cross compilers, this test is bogus. For G++, we can use various
45 dnl other compile line options to get a decent idea that the cross compiler
50 dnl Transform the name of the compiler to it's cross variant, unless
87 AC_MSG_ERROR(${CXX} is a non-working cross compiler)
97 AC_MSG_CHECKING([whether the G++ compiler ($CXX $CXXFLAGS $LDFLAGS) is a cross-compiler])
104 dnl Find a working GCC cross compiler. This only works for the GNU gcc compiler.
140 dnl to get a correct fully linked executable with a cross
[all …]
|
| /netbsd/src/external/gpl3/gcc/dist/config/ |
| D | acinclude.m4 | 6 dnl We are probably using a cross compiler, which will not be able to fully
8 dnl Find a working G++ cross compiler. This only works for the GNU C++ compiler.
43 dnl to get a correct fully linked executable with a cross compiler. For
44 dnl most cross compilers, this test is bogus. For G++, we can use various
45 dnl other compile line options to get a decent idea that the cross compiler
50 dnl Transform the name of the compiler to it's cross variant, unless
87 AC_MSG_ERROR(${CXX} is a non-working cross compiler)
97 AC_MSG_CHECKING([whether the G++ compiler ($CXX $CXXFLAGS $LDFLAGS) is a cross-compiler])
104 dnl Find a working GCC cross compiler. This only works for the GNU gcc compiler.
140 dnl to get a correct fully linked executable with a cross
[all …]
|
| /netbsd/src/external/gpl3/gdb/dist/config/ |
| D | acinclude.m4 | 6 dnl We are probably using a cross compiler, which will not be able to fully
8 dnl Find a working G++ cross compiler. This only works for the GNU C++ compiler.
43 dnl to get a correct fully linked executable with a cross compiler. For
44 dnl most cross compilers, this test is bogus. For G++, we can use various
45 dnl other compile line options to get a decent idea that the cross compiler
50 dnl Transform the name of the compiler to it's cross variant, unless
87 AC_MSG_ERROR(${CXX} is a non-working cross compiler)
97 AC_MSG_CHECKING([whether the G++ compiler ($CXX $CXXFLAGS $LDFLAGS) is a cross-compiler])
104 dnl Find a working GCC cross compiler. This only works for the GNU gcc compiler.
140 dnl to get a correct fully linked executable with a cross
[all …]
|
| /netbsd/src/external/gpl3/gcc/dist/gcc/cp/ |
| D | Make-lang.in | 23 # foo.all.cross, foo.start.encap, foo.rest.encap,
48 # to do the right thing within all.cross.
86 # Create a version of the g++ driver which calls the cross-compiler.
87 g++-cross$(exeext): xg++$(exeext)
88 -rm -f g++-cross$(exeext)
89 cp xg++$(exeext) g++-cross$(exeext)
173 c++.all.cross: g++-cross$(exeext)
262 if [ ! -f g++-cross$(exeext) ] ; then \
316 -rm -f xg++$(exeext) g++-cross$(exeext) cc1plus$(exeext) cc1plus.fda
|
| /netbsd/src/external/bsd/flex/dist/ |
| D | configure.ac | 76 # (e.g. when cross-compiling flex or when bootstrapping has bugs).
77 # Ideally we should be able to bootstrap even when cross-compiling.
147 dnl Autoconf bug: AC_FUNC_MALLOC and AC_FUNC_REALLOC might not warn of cross
151 AC_MSG_WARN([result $ac_cv_func_malloc_0_nonnull guessed because of cross compilation]))
154 AC_MSG_WARN([result $ac_cv_func_realloc_0_nonnull guessed because of cross compilation]))
|
| /netbsd/src/external/bsd/wpa/dist/wpa_supplicant/wpa_gui-qt4/ |
| D | wpa_gui.pro | 15 # cross compilation to win32
21 # cross compilation to win32
|
| /netbsd/src/external/gpl3/gdb/dist/gdb/doc/ |
| D | Doxyfile-gdb-xref.in | 3 # Doxygen file for a full GDB cross-reference.
39 # Build a full cross-reference.
|
| D | Doxyfile-gdbserver.in | 3 # Doxygen file for a GDBserver cross-reference.
38 # Build a full cross-reference.
|
| /netbsd/src/crypto/external/bsd/openssl/dist/ |
| D | NOTES-WINDOWS.md | 20 MinGW cross compiler
158 MinGW offers an alternative way to build native OpenSSL, by cross compilation.
198 In this case configure with the corresponding `--cross-compile-prefix=`
201 ./Configure mingw --cross-compile-prefix=i686-w64-mingw32- ...
205 ./Configure mingw64 --cross-compile-prefix=x86_64-w64-mingw32- ...
208 mingw[64] cross compilation.
|
| D | NOTES-NONSTOP.md | 111 Your `PATH` must include the bin directory for the c99 cross-compiler, as in:
115 This should be set before Configure is run. For the c99 cross-compiler to work
126 Do not forget to include any OpenSSL cross-compiling prefix and certificate
134 **Note:** In the event that you are attempting a FIPS-compliant cross-compile,
136 cross-compiles as the compilers do not necessarily generate identical objects.
141 point or another. If you are successful in your cross-compile efforts, please
150 of OpenSSL cannot be cross-compiled.
|
| /netbsd/src/external/gpl3/gcc/dist/libobjc/ |
| D | configure.ac | 45 AC_ARG_WITH(cross-host,
46 [ --with-cross-host=HOST configuring with a cross compiler])
94 # Install a library built with a cross compiler in tooldir, not libdir.
189 # Sanity check for the cross-compilation case:
341 dnl assume no system boehm-gc for cross builds ...
|
| /netbsd/src/external/gpl3/gcc/dist/libstdc++-v3/ |
| D | configure.ac | 23 # cross compilers, just think about it for a little while. :-)
25 # Also, if v3 is being configured as part of a cross compiler, the top-level
37 # We are being configured with some form of cross compiler.
151 # Eliminate -lstdc++ addition to postdeps for cross compiles.
214 # Checking with C++ can break a canadian cross build if either
304 # This lets us hard-code the functionality we know we'll have in the cross
318 # If Canadian cross, then don't pick up tools from the build directory.
614 # Determine cross-compile flags and AM_CONDITIONALs.
|
| /netbsd/src/external/bsd/pcc/dist/pcc/ |
| D | configure.ac | 323 # quick hack for cross-build to win32 host
445 [Build the compiler as a native rather than cross-build compiler]),
487 # setup for building a cross-compiler
568 # setup for cross-compiling mkext
571 AC_MSG_RESULT([cross compiling])
574 AC_MSG_RESULT([not cross compiling])
|
| /netbsd/src/external/gpl3/gcc/dist/libgcc/config/i386/ |
| D | t-dlldir-x | 1 # In a cross build, bindir contains host not target binaries, so target DLLs
|
| /netbsd/src/crypto/external/bsd/heimdal/dist/cf/ |
| D | check-compile-et.m4 | 61 krb_cv_com_err="cross"
90 elif test "${krb_cv_com_err}" = "cross"; then
|
| /netbsd/src/external/gpl2/xcvs/dist/m4/ |
| D | fnmatch.m4 | 21 dnl So we run a test program. If we are cross-compiling, take no chance.
48 [$2=cross])])
|