Lines Matching +full:binutils +full:- +full:powerpc64 +full:- +full:linux +full:- +full:gnu
7 itself, which is useful for upgrading an existing musl-based system or
8 compiler toolchain, or for using the provided musl-gcc wrapper with an
9 existing non-musl-based compiler.
11 Building complete native or cross-compiler toolchains is outside the
17 -------------------
19 The only build-time prerequisites for musl are GNU Make and a
21 set architecture and ABI, with support for a minimal subset of "GNU C"
22 extensions consisting mainly of gcc-style inline assembly, weak
23 aliases, hidden visibility, and stand-alone assembly source files.
27 binutils) versions should be used if possible since some older
30 The system used to build musl does not need to be Linux-based, nor do
31 the Linux kernel headers need to be available.
36 -----------------
50 * EABI, standard or hard-float VFP variant
51 * Little-endian default; big-endian variants also supported
55 * Little-endian default; big-endian variants also supported
59 * Big-endian default; little-endian variants also supported
60 * Default ABI variant uses FPU registers; alternate soft-float ABI
62 * MIPS2 or later, or kernel emulation of ll/sc (standard in Linux)
68 * Big-endian default; little-endian variants also supported
69 * Default ABI variant uses FPU registers; alternate soft-float ABI
73 * Compiler toolchain must provide 64-bit long double, not IBM
74 double-double or IEEE quad
78 * PowerPC64
80 * Compiler toolchain must provide 64-bit long double, not IBM
81 double-double or IEEE quad
85 * S390X (64-bit S390)
88 * Standard ELF ABI or FDPIC ABI (shared-text without MMU)
89 * Little-endian by default; big-endian variant also supported
90 * Full FPU ABI or soft-float ABI is supported, but the
91 single-precision-only FPU ABI is not
94 * Big-endian default; little-endian variants also supported
95 * Soft-float
100 * RISC-V 64
102 * Hard, soft, and hard-single/soft-double floating point ABIs
103 * Standard ELF; no shared-text NOMMU support
108 --------------------------------
112 1. Run the provided configure script from the top-level source
130 you're upgrading libc on an existing musl-based system. Doing so will
137 ------------------------
140 of the installation prefix: /lib/ld-musl-$ARCH.so.1. This is the
141 dynamic linker. Its pathname is hard-coded into all dynamic-linked
145 /lib/ld-linux.so.2 on i386 systems.
149 privileges), the --syslibdir option to configure can be used to
154 /etc/ld-musl-$ARCH.path (where $ARCH matches the architecture name
158 non-default location, the path file also needs to reside at that
162 passing --disable-shared to configure; this also cuts the build time
168 ------------------------------------
170 After installing, you should be able to use musl via the musl-gcc
181 /usr/local/musl/bin/musl-gcc hello.c
184 To configure autoconf-based program to compile and link against musl,
185 set the CC variable to musl-gcc when running configure, as in:
187 CC=musl-gcc ./configure ...
189 You will probably also want to use --prefix when building libraries to