3 This is the GRUB. Welcome.
5 This file contains instructions for compiling and installing the GRUB.
10 GRUB depends on some software packages installed into your system. If
11 you don't have any of them, please obtain and install them before
15 Note: older versions may work but support is limited
16 Note: clang 3.2 or later works for i386 and x86_64 targets but results in
18 earlier versions not tested
19 Note: clang 3.2 or later works for arm
20 earlier versions not tested
21 Note: clang 3.3 or later works for mips(el)
22 earlier versions fail to generate .reginfo and hence gprel relocations
24 Note: clang 3.4 or later works for powerpc
25 earlier versions suffer from vacopy bug (#15286)
27 * GNU Bison 2.3 or later
28 * GNU gettext 0.17 or later
29 * GNU binutils 2.9.1.0.23 or later
30 * Flex 2.5.35 or later
31 * Other standard GNU/Unix tools
33 On GNU/Linux, you also need:
35 * libdevmapper 1.02.34 or later (recommended)
37 For optional grub-emu features, you need:
40 * libpciaccess (optional)
43 To build GRUB's graphical terminal (gfxterm), you need:
48 If you use a development snapshot or want to hack on GRUB you may
51 * Python 2.5.2 or later
52 * Autoconf 2.60 or later
53 * Automake 1.10.1 or later
54 * Autogen 5.10 or later
56 Prerequisites for make-check:
58 * qemu, specifically the binary 'qemu-system-i386'
59 * xorriso 1.2.9 or later, for grub-mkrescue and grub-shell
64 The `configure' shell script attempts to guess correct values for
65 various system-dependent variables used during compilation. It uses
66 those values to create a `Makefile' in each directory of the package.
67 It may also create one or more `.h' files containing system-dependent
68 definitions. Finally, it creates a shell script `config.status' that
69 you can run in the future to recreate the current configuration, a
70 file `config.cache' that saves the results of its tests to speed up
71 reconfiguring, and a file `config.log' containing compiler output
72 (useful mainly for debugging `configure').
74 If you need to do unusual things to compile the package, please try to
75 figure out how `configure' could check whether to do them, and mail
76 diffs or instructions to the address given in the `README' so they can
77 be considered for the next release. If at some point `config.cache'
78 contains results you don't want to keep, you may remove or edit it.
80 The file `configure.ac' is used to create `configure' by a program
81 called `autoconf'. You only need `configure.in' if you want to change
82 it or regenerate `configure' using a newer version of `autoconf'.
88 The simplest way to compile this package is:
90 1. `cd' to the directory containing the package's source code.
92 2. Skip this and following step if you use release tarball and proceed to
93 step 4. If you want translations type `./linguas.sh'.
95 3. Type `./autogen.sh'.
97 4. Type `./configure' to configure the package for your system.
98 If you're using `csh' on an old version of System V, you might
99 need to type `sh ./configure' instead to prevent `csh' from trying
100 to execute `configure' itself.
102 Running `configure' takes awhile. While running, it prints some
103 messages telling which features it is checking for.
105 6. Type `make' to compile the package.
107 7. Optionally, type `make check' to run any self-tests that come with
110 8. Type `make install' to install the programs and any data files and
113 9. You can remove the program binaries and object files from the
114 source code directory by typing `make clean'. To also remove the
115 files that `configure' created (so you can compile the package for
116 a different kind of computer), type `make distclean'. There is
117 also a `make maintainer-clean' target, but that is intended mainly
118 for the package's developers. If you use it, you may have to get
119 all sorts of other programs in order to regenerate files that came
120 with the distribution.
122 Cross-compiling the GRUB
123 ========================
125 GRUB defines 3 platforms:
127 - "Build" is the one which build systems runs on.
128 - "Host" is where you execute GRUB utils.
129 - "Target" is where GRUB itself runs.
131 For grub-emu host and target must be the same but may differ from build.
133 If build and host are different make check isn't available.
135 If build and host are different man pages are not generated.
137 As an example imagine you have a build system running on FreeBSD on sparc
138 which prepares packages for developpers running amd64 GNU/Linux laptop and
139 they need to make images for ARM board running U-boot. In this case:
141 build=sparc64-freebsd
145 For this example the configure line might look like (more details below)
146 (some options are optional and included here for completeness but some rarely
147 used options are omited):
149 ./configure BUILD_CC=gcc BUILD_FREETYPE=freetype-config --host=amd64-linux-gnu
150 CC=amd64-linux-gnu-gcc CFLAGS="-g -O2" FREETYPE=amd64-linux-gnu-freetype-config
151 --target=arm --with-platform=uboot TARGET_CC=arm-elf-gcc
152 TARGET_CFLAGS="-Os -march=armv6" TARGET_CCASFLAGS="-march=armv6"
153 TARGET_OBJCOPY="arm-elf-objcopy" TARGET_STRIP="arm-elf-strip"
154 TARGET_NM=arm-elf-nm TARGET_RANLIB=arm-elf-ranlib LEX=gflex
156 You need to use following options to specify tools and platforms. For minimum
157 version look at prerequisites. All tools not mentioned in this section under
158 corresponding platform are not needed for the platform in question.
161 1. BUILD_CC= to gcc able to compile for build. This is used, for
162 example, to compile build-gentrigtables which is then run to
163 generate sin and cos tables.
164 2. BUILD_CFLAGS= for C options for build.
165 3. BUILD_CPPFLAGS= for C preprocessor options for build.
166 4. BUILD_FREETYPE= for freetype-config for build (optional).
169 1. --host= to autoconf name of host.
170 2. CC= for gcc able to compile for host
171 3. CFLAGS= for C options for host.
172 4. CPPFLAGS= for C preprocessor options for host.
173 5. LDFLAGS= for linker options for host.
174 6. FREETYPE= for freetype-config for host (optional).
175 7. Libdevmapper if any must be in standard linker folders (-ldevmapper) (optional).
176 8. Libfuse if any must be in standard linker folders (-lfuse) (optional).
177 9. Libzfs if any must be in standard linker folders (-lzfs) (optional).
178 10. Liblzma if any must be in standard linker folders (-llzma) (optional).
181 1. --target= to autoconf cpu name of target.
182 2. --with-platform to choose firmware.
183 3. TARGET_CC= for gcc able to compile for target
184 4. TARGET_CFLAGS= for C options for target.
185 5. TARGET_CPPFLAGS= for C preprocessor options for target.
186 6. TARGET_CCASFLAGS= for assembler options for target.
187 7. TARGET_LDFLAGS= for linker options for target.
188 8. TARGET_OBJCOPY= for objcopy for target.
189 9. TARGET_STRIP= for strip for target.
190 10. TARGET_NM= for nm for target.
191 11. TARGET_RANLIB= for ranlib for target.
193 - Additionally for emu, for host and target.
194 1. SDL is looked for in stadard linker directories (-lSDL) (optional)
195 2. libpciaccess is looked for in stadard linker directories (-lpciaccess) (optional)
196 3. libusb is looked for in stadard linker directories (-lusb) (optional)
198 - Platform-agnostic tools and data.
199 1. make is the tool you execute after ./configure.
200 2. Bison is specified in YACC= variable
201 3. Flex is specified in LEX= variable
202 4. GNU unifont and Djvu sans are looked for in standard directories.
204 Compiling For Multiple Architectures
205 ====================================
207 You can compile the package for more than one kind of computer at the
208 same time, by placing the object files for each architecture in their
209 own directory. `cd' to the directory where you want the object files
210 and executables to go and run the `configure' script. `configure'
211 automatically checks for the source code in the directory that
212 `configure' is in and in `..'.
218 By default, `make install' will install the package's files in
219 `/usr/local/bin', `/usr/local/man', etc. You can specify an
220 installation prefix by giving `configure' the option `--prefix=PATH'.
222 You can specify separate installation prefixes for
223 architecture-specific files and architecture-independent files. If
224 you give `configure' the option `--exec-prefix=PATH', the package will
225 use PATH as the prefix for installing programs and libraries.
226 Documentation and other data files will still use the regular prefix.
228 In addition, if you use an unusual directory layout you can give
229 options like `--bindir=PATH' to specify different values for
230 particular kinds of files. Run `configure --help' for a list of the
231 directories you can set and what kinds of files go in them.
233 If the package supports it, you can cause programs to be installed
234 with an extra prefix or suffix on their names by giving `configure'
235 the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
237 Please note, however, that the GRUB knows where it is located in the
238 filesystem. If you have installed it in an unusual location, the
239 system might not work properly, or at all. The chief utility of these
240 options for the GRUB is to allow you to "install" in some alternate
241 location, and then copy these to the actual root filesystem later.
247 If you want to set default values for `configure' scripts to share,
248 you can create a site shell script called `config.site' that gives
249 default values for variables like `CC', `cache_file', and `prefix'.
250 `configure' looks for `PREFIX/share/config.site' if it exists, then
251 `PREFIX/etc/config.site' if it exists. Or, you can set the
252 `CONFIG_SITE' environment variable to the location of the site script.
253 A warning: not all `configure' scripts look for a site script.
259 `configure' recognizes the following options to control how it
263 Use and save the results of the tests in FILE instead of
264 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
265 debugging `configure'.
268 Print a summary of the options to `configure', and exit.
273 Do not print messages saying which checks are being made.
276 Look for the package's source code in directory DIR. Usually
277 `configure' can determine that directory automatically.
280 Print the version of Autoconf used to generate the `configure'