Searched full:cross (Results 1 – 25 of 2451) sorted by relevance
12345678910>>...99
... perl-cross-1.3.5/Makefile perl-cross-1.3.5/Makefile.config.
2 # Example config for cross compiling33 OUTPUT_DIR = ${THIS_DIR}/cross-compile45 # The log file is stored in the OUTPUT_DIR called cross.log47 LOG_FILE = ${OUTPUT_DIR}/cross.log78 MAKE_CMD = PATH=/usr/local/gcc-${GCC_VER}-nolibc/${CROSS}/bin:$PATH CROSS_COMPILE=${CROSS}- make AR…85 # all cross compiles with PREEMPT set, or TRACING on, etc.91 # The test names will have the arch and cross compiler used. This will be shown in93 TEST_NAME = ${ARCH} ${CROSS}97 # Notice that CROSS and ARCH are also options and not variables (again '=' instead101 CROSS = alpha-linux[all …]
1 SUMMARY = "Perl-cross build system"2 HOMEPAGE = "https://github.com/arsv/perl-cross"3 DESCRIPTION = "perl-cross provides configure script, top-level Makefile and some auxiliary files fo…4 with the primary emphasis on cross-compiling the source."7 # README.md is taken from https://github.com/arsv/perl-cross/blob/master/README.md13 SRC_URI = "https://github.com/arsv/perl-cross/releases/download/${PV}/perl-cross-${PV}.tar.gz;name=…15 file://0001-perl-cross-add-LDFLAGS-when-linking-libperl.patch \19 UPSTREAM_CHECK_URI = "https://github.com/arsv/perl-cross/releases/"21 SRC_URI[perl-cross.sha256sum] = "77f13ca84a63025053852331b72d4046c1f90ded98bd45ccedea738621907335"23 S = "${WORKDIR}/perl-cross-${PV}"[all …]
47 # Three methods for waf cross compile:49 # Only --cross-answers - try the cross-answers file, and if53 # Only --cross-execute - get the answer from cross-execute,54 # an emulator (qemu) is used to run cross-compiled binaries.59 # Try the cross-answers file first, and if there is no60 # corresponding answer, use cross-execute to get an answer,65 # to help generate the cross answer when adding new board support.70 # Prepare the cross-answers file71 WAF_CROSS_ANSWERS_PATH="${THISDIR}/../../files/waf-cross-answers"72 CROSS_ANSWERS="${B}/cross-answers-${TARGET_ARCH}.txt"[all …]
4 Subject: [PATCH] eglibc: Cross building and testing instructions11 GLIBC.cross-building | 383 +++++++++++++++++++++++++++++++++++++++++++12 GLIBC.cross-testing | 205 +++++++++++++++++++++++14 create mode 100644 GLIBC.cross-building15 create mode 100644 GLIBC.cross-testing17 diff --git a/GLIBC.cross-building b/GLIBC.cross-building21 +++ b/GLIBC.cross-building25 + Cross-Compiling GLIBC33 +process of cross-compiling the GNU C library is quite a bit more36 +1) Build a cross-compiler, with certain facilities disabled.[all …]
1 **perl-cross** provides configure script, top-level Makefile3 with the primary emphasis on cross-compiling the source. 5 # Get perl and perl-cross sources7 curl -L -O https://github.com/arsv/perl-cross/releases/download/1.1.3/perl-cross-1.1.3.tar.gz9 # Unpack perl-cross over perl, overwriting Makefile12 tar --strip-components=1 -zxf ../perl-cross-1.1.3.tar.gz23 Check [project pages](http://arsv.github.io/perl-cross/) for more info. 24 In particular, [configure usage](http://arsv.github.io/perl-cross/usage.html)27 Perl-cross is a free software licensed under the same terms
6 We need to be able to trigger configure's cross code but we don't want22 echo "strip = [$(meson_quote $strip)]" >> $cross23 echo "windres = [$(meson_quote $windres)]" >> $cross25 cross_arg="--cross-file config-meson.cross"26 echo "[host_machine]" >> $cross30 echo "endian = 'little'" >> $cross33 - cross_arg="--native-file config-meson.cross"35 mv $cross config-meson.cross
2 Subject: [PATCH] enable cross compilation for expect5 and inserting the results into the cross compilation section of19 - AC_MSG_ERROR([Expect can't be cross compiled])28 - AC_MSG_ERROR([Expect can't be cross compiled])38 -, AC_MSG_WARN([Expect can't be cross compiled])47 - AC_MSG_ERROR([Expect can't be cross compiled])56 - AC_MSG_ERROR([Expect can't be cross compiled])67 - AC_MSG_ERROR([Expect can't be cross compiled])78 - AC_MSG_ERROR([Expect can't be cross compiled])87 - AC_MSG_ERROR([Expect can't be cross compiled])[all …]
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks43 6) cross-directory rename. The trickiest in the whole bunch. Locking74 (1) if object removal or non-cross-directory rename holds lock on A and76 acquire the lock on B. (Proof: only cross-directory rename can change79 (2) if cross-directory rename holds the lock on filesystem, order will not80 change until rename acquires all locks. (Proof: other cross-directory104 Any contended object is either held by cross-directory rename or106 operation other than cross-directory rename. Then the lock this operation109 It means that one of the operations is cross-directory rename.112 own descendent. Moreover, there is exactly one cross-directory rename[all …]
1 Allow cross compiling.13 - AC_MSG_ERROR([Expect can't be cross compiled])22 - AC_MSG_ERROR([Expect can't be cross compiled])33 -, AC_MSG_WARN([Expect can't be cross compiled])43 - AC_MSG_ERROR([Expect can't be cross compiled])54 - AC_MSG_ERROR([Expect can't be cross compiled])65 - AC_MSG_ERROR([Expect can't be cross compiled])76 - AC_MSG_ERROR([Expect can't be cross compiled])85 - AC_MSG_ERROR([Expect can't be cross compiled])94 - AC_MSG_ERROR([Expect can't be cross compiled])[all …]
5 PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}binutils = "binutils-cross-${TARGET_ARCH}"6 PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}gcc = "gcc-cross-${TARGET_ARCH}"7 PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}g++ = "gcc-cross-${TARGET_ARCH}"33 PREFERRED_VERSION_gcc-cross-${TARGET_ARCH} ?= "${GCCVERSION}"35 PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} ?= "${GCCVERSION}"48 PREFERRED_VERSION_binutils-cross-${TARGET_ARCH} ?= "${BINUVERSION}"50 PREFERRED_VERSION_binutils-cross-canadian-${TRANSLATED_TARGET_ARCH} ?= "${BINUVERSION}"52 PREFERRED_VERSION_gdb-cross-${TARGET_ARCH} ?= "${GDBVERSION}"53 PREFERRED_VERSION_gdb-cross-canadian-${TRANSLATED_TARGET_ARCH} ?= "${GDBVERSION}"73 PREFERRED_VERSION_go-cross-${TUNE_PKGARCH} ?= "${GOVERSION}"[all …]
14 file://0001-Makefile-for-cross-compile-SoftFloat.patch \15 file://0002-Makefile-for-cross-compile-TestFloat.patch \25 oe_runmake -C SoftFloat-${PV}/build/Linux-Cross-Compile/26 oe_runmake -C TestFloat-${PV}/build/Linux-Cross-Compile/31 install ${S}/TestFloat-${PV}/build/Linux-Cross-Compile/testfloat ${D}/${bindir}32 install ${S}/TestFloat-${PV}/build/Linux-Cross-Compile/testfloat_gen ${D}/${bindir}33 install ${S}/TestFloat-${PV}/build/Linux-Cross-Compile/testfloat_ver ${D}/${bindir}34 install ${S}/TestFloat-${PV}/build/Linux-Cross-Compile/testsoftfloat ${D}/${bindir}35 install ${S}/TestFloat-${PV}/build/Linux-Cross-Compile/timesoftfloat ${D}/${bindir}
7 -# If you are running a cross compiler, you may want to set this10 -CROSS = #/usr/i386-linux-uclibc/usr/bin/i386-uclibc-11 -CC = $(CROSS)gcc12 -LD = $(CROSS)gcc13 -AR = $(CROSS)ar14 -STRIP = $(CROSS)strip15 -RANLIB = $(CROSS)ranlib26 -export CROSS CC AR STRIP RANLIB CFLAGS LDFLAGS LIB_OBJS
1 SUMMARY = "Host SDK package for Rust cross canadian toolchain"2 PN = "packagegroup-rust-cross-canadian-${MACHINE}"4 inherit cross-canadian packagegroup8 RUST="rust-cross-canadian-${TRANSLATED_TARGET_ARCH}"9 CARGO="cargo-cross-canadian-${TRANSLATED_TARGET_ARCH}"10 RUST_TOOLS="rust-tools-cross-canadian-${TRANSLATED_TARGET_ARCH}"15 rust-cross-canadian-src \
1 SUMMARY = "Host SDK package for cross canadian toolchain"2 PN = "packagegroup-cross-canadian-${MACHINE}"4 inherit cross-canadian packagegroup9 BINUTILS = "binutils-cross-canadian-${TRANSLATED_TARGET_ARCH}"10 GCC = "gcc-cross-canadian-${TRANSLATED_TARGET_ARCH}"11 GDB = "gdb-cross-canadian-${TRANSLATED_TARGET_ARCH}"21 # cross-canadian.bbclass prevents variable dependency propagation to TRANSLATED_TARGET_ARCH
4 Subject: [PATCH] setup.py: Do not detect multiarch paths when cross-compiling7 to operate, which is not good when cross compiling, since it ends up11 -I/usr/include/aarch64-linux-gnu during cross compile and since arches12 are so similar, cross compiler (epecially clang) is inhererently configured16 compiles when using cross gcc.18 Fixes python3 cross build by not running this funciton when cross compiling31 # only change this for cross builds for 3.3, issues on Mageia
13 Once you have a suitable :ref:`sdk-manual/intro:the cross-development toolchain`77 2. *Source the Cross-Toolchain Environment Setup File:* As described78 earlier in the manual, installing the cross-toolchain creates a79 cross-toolchain environment setup script in the directory that the107 4. *Cross-Compile the Project:* This command compiles the project using108 the cross-compiler. The116 project, you can use the cross-toolchain by just passing the119 directory in which you installed the cross-toolchain. For example,124 the appropriate cross-toolchain tools::137 cross-toolchain environment setup script and how they are used or[all …]
6 order to describe the userspace API and to generate cross-references7 between the code and the documentation. Adding cross-references for12 cross-references. It has to be called via Makefile, while building the26 enums and defines and create cross-references to a Sphinx book.65 included via ..parsed-literal block with cross-references for the73 enums and enum symbols and create cross-references for all of them.84 The \ **ignore**\ means that it won't generate cross references for a92 The \ **replace**\ means that it will generate cross references for a162 It won't generate cross-references for \ **PRIVATE**\ .172 It will make the BAR1 and BAR2 enum symbols to cross reference the foo
2 # texinfo utilities at build-time. Native and cross recipes are made to use the11 TEXDEP:class-cross = "texinfo-dummy-native"13 TEXDEP:class-cross-canadian = "texinfo-dummy-native"16 # libtool-cross doesn't inherit cross17 TEXDEP:pn-libtool-cross = "texinfo-dummy-native"
18 # -C prefix specify command prefix for cross-building tools50 # cross-compilation prefix51 CROSS=67 echo ' [-c] [-C cross-prefix] [-D datadir] [-W workingdir]' >&2127 CROSS="$1"192 LANG=C elfformat="`${CROSS}objdump -p "$kernel" | grep 'file format' | awk '{print $4}'`"216 LD_VERSION=$(${CROSS}ld --version | ld_version)371 ${CROSS}objcopy $objflags "$kernel" "$vmz.$$"424 version=`${CROSS}strings "$kernel" | grep '^Linux version [-0-9.]' | \431 membase=`${CROSS}objdump -p "$kernel" | grep -m 1 LOAD | awk '{print $7}'`[all …]
1 SUMMARY = "Cross locale generation tool for glibc"28 file://0010-eglibc-Cross-building-and-testing-instructions.patch \29 file://0011-eglibc-Help-bootstrap-cross-toolchain.patch \31 file://0013-eglibc-Forward-port-cross-locale-generation-support.patch \52 install -m 0755 ${B}/localedef ${D}${bindir}/cross-localedef53 install -m 0755 ${B}/cross-localedef-hardlink ${D}${bindir}/cross-localedef-hardlink
12 bool "Build cross gdb for the host"14 # allow to build a cross-gdb, as the one of the external19 Build a cross gdb that runs on the host machine and debugs34 This option enables the Python 3 support in the cross gdb.40 This option enables the simulator support in the cross gdb.66 # If cross-gdb is not enabled, the latest stable version is chosen.
6 Buildroot allows to do cross-debugging, where the debugger runs on the14 +BR2_PACKAGE_GDB_SERVER+. This ensures that both the cross gdb and20 external toolchain does not have a cross gdb or gdbserver, it is also32 from the cross gdb.34 Then, on the host, you should start the cross gdb using the following47 cross gdb where to find the libraries of the target.49 Finally, to connect to the target from the cross gdb:
2 require rust-cross-canadian-common.inc4 RUSTLIB_TARGET_PN = "rust-cross-canadian-rustlib-target-${TRANSLATED_TARGET_ARCH}"5 RUSTLIB_HOST_PN = "rust-cross-canadian-rustlib-host-${TRANSLATED_TARGET_ARCH}"6 RUSTLIB_SRC_PN = "rust-cross-canadian-src"8 PN = "rust-cross-canadian-${TRANSLATED_TARGET_ARCH}"74 SUMMARY:${RUSTLIB_TARGET_PN} = "Rust cross canadian libaries for ${TARGET_SYS}"75 SUMMARY:${RUSTLIB_HOST_PN} = "Rust cross canadian libaries for ${HOST_SYS}"76 SUMMARY:${RUSTLIB_SRC_PN} = "Rust standard library sources for cross canadian toolchain"
40 // We define cross product only for 2d (see Wolfram) and 3d.42 // Generalisation of cross product to n-dimension is defined as43 // wedge product but it is not direct analogue to binary cross product.59 // For 2-dimensions, analog of the cross product U(x,y) and V(x,y) is in apply()87 \brief Computes the cross product of two vectors.92 \return the cross product vector107 \brief Computes the cross product of two vectors.112 \return the cross product vector