Searched full:build (Results 1 – 25 of 262) sorted by relevance
1234567891011
7 exactly the same. This makes it possible to verify that the build57 to an absolute filename in an out-of-tree build. Kbuild automatically67 The build processes for some programs under the ``tools/``69 cause a later source package build using e.g. ``make rpm-pkg`` to78 generate a different temporary key for each build, resulting in the82 One approach to this is to divide up the build process so that the91 Build the kernel and modules.96 4. Perform a second build that attaches the module signatures. It113 Once you set all the necessary variables for a reproducible build, a122 .. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp[all …]
5 This document describes how to build an out-of-tree kernel module.10 === 2 How to Build External Modules40 "kbuild" is the build system used by the Linux kernel. Modules must use41 kbuild to stay compatible with changes in the build infrastructure and50 complexity, so one only has to type "make" to build the module. This is55 2. How to Build External Modules58 To build external modules, you must have a prebuilt kernel available59 that contains the configuration and header files used in the build.69 NOTE: "modules_prepare" will not build Module.symvers even if70 CONFIG_MODVERSIONS is set; therefore, a full kernel build needs to be[all …]
42 --- 7.1 Set variables to tweak the build to the architecture90 .config file to construct various file lists used by kbuild to build94 are used to build the kernel based on the kbuild makefiles.102 *Users* are people who build kernels. These people type commands such as117 *Kbuild developers* are people who work on the kernel build system itself.211 that you want to build a module in the same way as above; however,212 kbuild needs to know which object files you want to build your245 kbuild will build an ext2.o file for you out of the individual290 Makefiles in these subdirs. The build system will automatically330 invocations happening during a recursive build.[all …]
30 - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave39 this mode. In this case, you should build the kernel with42 - Build the gdb scripts (required on kernels v5.1 and above)::55 - cd /path/to/linux-build62 add-auto-load-safe-path /path/to/linux-build78 scanning for modules in /home/user/linux/build79 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko80 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko81 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko82 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko[all …]
7 To get coverage data for a specific file, change to the kernel build119 Separated build and test machines130 gcc version used for kernel build. Also the following files need to be131 copied from build to test machine:136 from the build tree:142 exact same file system location on the test machine as on the build146 b) gcov is run on the BUILD machine149 to build machine:155 These files can be copied to any location on the build machine. gcov158 Example directory setup on the build machine::[all …]
29 To build the tests::37 To build and run the tests with a single command, use::49 To build, save output files in a separate directory with O= ::53 To build, save output files in a separate directory with KBUILD_OUTPUT ::80 You can specify multiple tests to build and run::84 To build, save output files in a separate directory with O= ::88 To build, save output files in a separate directory with KBUILD_OUTPUT ::114 To build the hotplug tests::195 * Don't break the build on any architecture, and209 TEST_CUSTOM_PROGS should be used by tests that require custom build[all …]
8 Format: %d.%d.%d.%d, type:major:minor:build.14 Detailed AudioDSP firmware build information including15 build hash and log-providers hash. This information is
15 Display Wilco Embedded Controller firmware build date.22 Display Wilco Embedded Controller build revision.58 and z is the build number. For example: 95.00.06
6 Contaminants build-up in the measurement chamber or optical22 Contaminants build-up in the measurement chamber or optical
17 Build instructions for OpenRISC toolchain and Linux20 In order to build and run Linux for OpenRISC, you'll need at least a basic28 or Stafford's toolchain build and release scripts.33 building https://github.com/stffrdhrn/or1k-toolchain-build38 Build the Linux kernel as usual::47 development board with the OpenRISC SoC. During the build FPGA RTL is code58 fusesoc build de0_nano72 Linux running on QEMU. You can build QEMU yourself, but your Linux distribution
98 build system (more on this in the next section). However, for board families106 seamlessly with the build system, it's best to have this directory the same108 a family, the build system has ways of dealing with this (via incdir-y198 3. Hooking into the Build System203 whole mess to fit into the build system.205 Large portions of the build system are now entirely dynamic, and merely226 Next, the build system assumes that your include/asm-sh directory will also255 build target, and it will be implicitly listed as such in the help text.263 adx_defconfig Build for adx264 cqreek_defconfig Build for cqreek[all …]
37 build date 04/03/13 do not match the register locations in the Nuvoton61 Intel DH87RL NCT6683D EC firmware version 1.0 build 04/03/1362 Intel DH87MC NCT6683D EC firmware version 1.0 build 04/03/1363 Intel DB85FL NCT6683D EC firmware version 1.0 build 04/03/13
98 2. Build with CONFIG_HOTPLUG_CPU=y. After boot completes, force183 2. Build with CONFIG_HOTPLUG_CPU=y. Once boot completes, force the211 a. Build with CONFIG_NO_HZ=y and CONFIG_RCU_FAST_NO_HZ=y.246 a. Build your kernel with CONFIG_SLUB=y rather than256 be able to build your kernel with CONFIG_CPU_FREQ=n to277 e. If running on high-end powerpc servers, build with285 f. If running on Cell Processor, build your kernel with290 g. If running on PowerMAC, build your kernel with302 1. Build the kernel with CONFIG_PREEMPT=n. This prevents these306 2. Build the kernel with CONFIG_RCU_BOOST=n. This prevents these[all …]
124 build or operation.126 Build directory for the kernel136 build directory: /home/name/build/kernel138 To configure and build the kernel, use::141 make O=/home/name/build/kernel menuconfig142 make O=/home/name/build/kernel143 sudo make O=/home/name/build/kernel modules_install install271 build should require that. Don't take the name of root in vain.276 - Verbose kernel compile/build output:278 Normally, the kernel build system runs in a fairly quiet mode (but not[all …]
58 Sphinx\ [#f1]_ 1.3 sphinx-build --version61 .. [#f1] Sphinx is needed only to build the Kernel documentation84 You will need GNU make 3.81 or later to build the kernel.89 Binutils 2.23 or newer is needed to build the kernel.94 The build system, as of 4.18, requires pkg-config to check for installed102 Since Linux 4.16, the build system generates lexical analyzers103 during build. This requires flex 2.5.35 or later.109 Since Linux 4.16, the build system generates parsers110 during build. This requires bison 2.0 or later.116 ``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.[all …]
27 d) Any Documentation/ changes build successfully without new warnings/errors.28 Use ``make htmldocs`` or ``make pdfdocs`` to check the build and32 or some other build farm.75 13) Has been build- and runtime tested with and without ``CONFIG_SMP`` and
19 SPHINXBUILD = sphinx-build33 # User-friendly check for sphinx-build67 # $3 name of the build subfolder / e.g. "userspace-api/media", used as:75 …cmd_sphinx = $(MAKE) BUILDDIR=$(abspath $(BUILDDIR)) $(build)=Documentation/userspace-api/media $2…136 $(Q)$(MAKE) BUILDDIR=$(abspath $(BUILDDIR)) $(build)=Documentation/userspace-api/media clean154 @echo ' make SPHINX_CONF={conf-file} [target] use *additional* sphinx-build'155 @echo ' configuration. This is e.g. useful to build with nit-picking config.'
23 image. The details of the build system is discussed in the next section.97 built with 'make treeImage.walnut', then the build system will use98 arch/powerpc/boot/dts/walnut.dts to build treeImage.walnut.101 targets build all the default images as selected by the kernel configuration.111 images on a single build. The design decision was made to not use any114 kernel configuration. Building all the wrapper bits on every kernel build131 the target you are trying to build is supported by the wrapper bits.
105 (Inter-Integrated Circuit). In order to be able to build support210 Except if you know exactly what you're doing, or if you want to build296 Once the ``.config`` file has everything needed, all it takes to build311 some ways to build just the new drivers, using alternative trees.325 it would work (or even build) on a random Kernel. This tree is maintained330 add ``[PATCH media-build]`` at the e-mail's subject if you submit a new331 patch for the media-build.335 $ ./build339 1) you may need to run it twice if the ``media-build`` tree gets352 Then, you can build and install the new drivers::
23 Build chapter26 Once you pick up a Kernel source, you should configure, build,46 To build and install, you should run::
34 ``Multimedia support`` => ``Customise analog and hybrid tuner modules to build``53 => ``Customise the frontend modules to build`` ``Customise DVB frontends`` =>99 …#) ``Multimedia support`` => ``Customise analog and hybrid tuner modules to build`` => ``Simple tu…
33 The documentation build currently spews out an unbelievable number of43 Warnings from the documentation build almost always point at a real55 For example, in a documentation build I grabbed a pair of warnings nearly77 The problem is the missing "*", which confuses the build system's88 resulting in these doc-build warnings:137 from the documentation build, then we can start expecting developers to144 many of those comments are never pulled into the docs build. That makes156 documentation build unless they are placed in a document that is272 Non-LaTeX PDF build286 build, the world would be eternally grateful.
26 archive to be used as the image or have the kernel build process build41 The kernel build process can also build an early userspace image from121 and a number of other utilities, so you can replace kinit and build
135 It is sometimes desirable to torture RCU on a specific kernel build,136 for example, when preparing to put that kernel build into production.161 necessary to build a number of kernels in order to test that change172 complete, the resulting build products and console output are analyzed179 from about eight hours to about one hour (not counting the time to build224 Finally, the --trust-make argument allows each kernel build to reuse what225 it can from the previous kernel build.232 to a file. The build products and console output of each run is kept in259 This contains build output for a specific scenario.264 it might not exist if the build failed.