| /f-stack/dpdk/doc/guides/platform/ |
| H A D | octeontx.rst | 70 The OCTEON TX platform drivers can be compiled either natively on 71 **OCTEON TX** :sup:`®` board or cross-compiled on an x86 based platform. 80 If the kernel and modules are cross-compiled and copied to the target board, 83 native architecture, the linux sources need to be compiled once natively. 93 drivers can be compiled with the following steps, 100 The example applications can be compiled using the following: 110 The DPDK applications can be cross-compiled on any x86 based platform. The 133 The example applications can be compiled using the following:
|
| H A D | bluefield.rst | 54 DPDK can be compiled either natively on BlueField platforms or cross-compiled on 80 Such header files and libraries can be cross-compiled and installed on to the
|
| /f-stack/freebsd/contrib/openzfs/config/ |
| H A D | always-system.m4 | 9 [True if ZFS is to be compiled for a Linux system]) 14 [True if ZFS is to be compiled for a FreeBSD system])
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | bcmfs.rst | 63 To execute BCMFS PMD, it must be compiled with VFIO_PRESENT flag on the 66 The BCMFS PMD may be compiled natively on a Stingray platform or 67 cross-compiled on an x86 platform. For example, below commands can be executed
|
| H A D | octeontx.rst | 66 The OCTEON TX crypto poll mode driver can be compiled either natively on 67 **OCTEON TX** :sup:`®` board or cross-compiled on an x86 based platform.
|
| H A D | octeontx2.rst | 70 The OCTEON TX2 crypto PMD may be compiled natively on an OCTEON TX2 platform or 71 cross-compiled on an x86 platform.
|
| /f-stack/dpdk/doc/guides/freebsd_gsg/ |
| H A D | install_from_ports.rst | 50 a pre-compiled binary package. 64 These examples can be compiled and run as described in :ref:`compiling_sample_apps`. 74 To install a copy of the DPDK compiled using gcc, please download the 79 compiled and run as below, where we have 2 memory blocks of size 1G reserved
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | build_app.rst | 7 The ``testpmd`` application is compiled as part of the main compilation of the DPDK libraries and t…
|
| /f-stack/freebsd/contrib/libsodium/ |
| H A D | ChangeLog | 40 Webassembly code is loaded and compiled. 87 - The library can now be compiled with recent versions of 167 - The library can be compiled with recent Emscripten versions. 170 - The code can now be compiled on SLES11 service pack 4. 199 compiled on non-Intel platforms. 203 - The library can now be compiled on Minix. 227 compiled using Visual Studio. 252 - The library can now be compiled with the CompCert compiler. 466 - libsodium can now be cross-compiled to Windows from Linux. 467 - libsodium can now be compiled with emscripten. [all …]
|
| /f-stack/dpdk/examples/bpf/ |
| H A D | README | 5 Once compiled, these example programs can be loaded into `testpmd`
|
| /f-stack/freebsd/contrib/libsodium/packaging/dotnet-core/ |
| H A D | README.md | 7 In .NET Core, it is customary to provide pre-compiled binaries for all platforms 17 * For Linux, libsodium is compiled in Docker containers.
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | regexdev.rst | 120 The online mode means, that the rule database in being compiled by the 121 RegEx PMD while in the offline mode the rule database is compiled by external 130 Offline rule configuration can be done by adding a pointer to the compiled
|
| H A D | lto.rst | 18 compiler and the code that is being compiled.
|
| H A D | bpf_lib.rst | 26 * Provide information about natively compiled code for given BPF context.
|
| /f-stack/freebsd/mips/conf/ |
| H A D | MT7621_FDT | 39 # UART device support is compiled in when uart_ns8250 is selected (default)
|
| H A D | MT7628_FDT | 40 # UART device support is compiled in when uart_ns8250 is selected (default)
|
| /f-stack/freebsd/contrib/libsodium/src/libsodium/sodium/ |
| H A D | core.c | 34 # warning *** The library is being compiled using an undocumented method.
|
| /f-stack/freebsd/contrib/zstd/zlibWrapper/ |
| H A D | README.md | 23 Let's assume that your project that uses zlib is compiled with: 58 Then we have changed `#include "zlib.h"` to `#include "zstd_zlibwrapper.h"`, compiled the [example.… 83 The benchmark tool can be compiled with `make zwrapbench` using [zlibWrapper/Makefile](Makefile).
|
| /f-stack/app/redis-5.0.5/deps/hiredis/ |
| H A D | CHANGELOG.md | 7 * Fix warnings, when compiled with -Wshadow 74 The parser, standalone since v0.12.0, can now be compiled on Windows
|
| /f-stack/dpdk/devtools/ |
| H A D | check-includes.sh | 39 compiled with the strictest possible flags.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | axgbe.rst | 8 for AMD 10 Gbps family of adapters. It is compiled and tested in standard linux distro like Ubuntu.
|
| /f-stack/freebsd/contrib/zlib/contrib/asm686/ |
| H A D | README.686 | 12 compiled using gcc 2.7.2.3. Your mileage may vary.
|
| /f-stack/freebsd/contrib/zlib/ |
| H A D | README | 60 - For 64-bit Irix, deflate.c must be compiled without any optimization. With 65 when compiled with cc.
|
| H A D | FAQ | 16 The zlib sources can be compiled without change to produce a DLL. See the 189 Note that distributing a compiled zlib library along with zlib.h and 253 zlib is compiled. See the zlibCompileFlags() function in zlib.h. 262 compiled to use sprintf() or vsprintf(), then there is no protection 265 will not exceed 8K. On the other hand, if zlib is compiled to use
|
| /f-stack/freebsd/contrib/zstd/programs/ |
| H A D | README.md | 64 - __ZSTD_NOBENCH__ : `zstd` cli will be compiled without its integrated benchmark module. 68 - __ZSTD_NODICT__ : `zstd` cli will be compiled without support for the integrated dictionary build… 72 - __ZSTD_NOCOMPRESS__ : `zstd` cli will be compiled without support for compression. 77 - __ZSTD_NODECOMPRESS__ : `zstd` cli will be compiled without support for decompression. 225 This functionality only exists when `zstd` is compiled with multithread support.
|