]>
Commit | Line | Data |
---|---|---|
6a161fa9 | 1 | -*- Text -*- |
2 | ||
4b13b216 | 3 | This is the GRUB. Welcome. |
6a161fa9 | 4 | |
4b13b216 | 5 | This file contains instructions for compiling and installing the GRUB. |
6a161fa9 | 6 | |
7 | The Requirements | |
8 | ================ | |
9 | ||
4b13b216 | 10 | GRUB depends on some software packages installed into your system. If |
6a161fa9 | 11 | you don't have any of them, please obtain and install them before |
4b13b216 | 12 | configuring the GRUB. |
6a161fa9 | 13 | |
e30d87ad | 14 | * GCC 4.1.3 or later |
6a161fa9 | 15 | * GNU Make |
160034b2 | 16 | * GNU Bison 2.3 or later |
fc8345da | 17 | * GNU gettext 0.17 or later |
6a161fa9 | 18 | * GNU binutils 2.9.1.0.23 or later |
7d8c0213 | 19 | * Flex 2.5.35 or later |
6a161fa9 | 20 | * Other standard GNU/Unix tools |
86e5b1db | 21 | |
795b593a CW |
22 | On GNU/Linux, you also need: |
23 | ||
efa1bee7 | 24 | * libdevmapper 1.02.34 or later (recommended) |
795b593a | 25 | |
db99fbe8 | 26 | For optional grub-emu features, you need: |
795b593a | 27 | |
795b593a | 28 | * SDL (recommended) |
db99fbe8 VS |
29 | * libpciaccess (optional) |
30 | * libusb (optional) | |
795b593a CW |
31 | |
32 | To build GRUB's graphical terminal (gfxterm), you need: | |
33 | ||
34 | * FreeType 2 or later | |
35 | * GNU Unifont | |
36 | ||
86e5b1db | 37 | If you use a development snapshot or want to hack on GRUB you may |
38 | need the following. | |
39 | ||
8d20dcfc | 40 | * Python 2.5.2 or later |
f022876b | 41 | * Autoconf 2.60 or later |
37fb845b | 42 | * Automake 1.10.1 or later |
ff174dbe | 43 | * Autogen 5.10 or later |
6a161fa9 | 44 | |
fc8345da JU |
45 | Prerequisites for make-check: |
46 | ||
47 | * qemu, specifically the binary 'qemu-system-i386' | |
8ca86b3a | 48 | * xorriso 1.2.9 or later, for grub-mkrescue and grub-shell |
fc8345da | 49 | |
4b13b216 | 50 | Configuring the GRUB |
6a161fa9 | 51 | ==================== |
52 | ||
53 | The `configure' shell script attempts to guess correct values for | |
54 | various system-dependent variables used during compilation. It uses | |
55 | those values to create a `Makefile' in each directory of the package. | |
56 | It may also create one or more `.h' files containing system-dependent | |
57 | definitions. Finally, it creates a shell script `config.status' that | |
58 | you can run in the future to recreate the current configuration, a | |
59 | file `config.cache' that saves the results of its tests to speed up | |
60 | reconfiguring, and a file `config.log' containing compiler output | |
61 | (useful mainly for debugging `configure'). | |
62 | ||
63 | If you need to do unusual things to compile the package, please try to | |
64 | figure out how `configure' could check whether to do them, and mail | |
65 | diffs or instructions to the address given in the `README' so they can | |
66 | be considered for the next release. If at some point `config.cache' | |
67 | contains results you don't want to keep, you may remove or edit it. | |
68 | ||
69 | The file `configure.ac' is used to create `configure' by a program | |
70 | called `autoconf'. You only need `configure.in' if you want to change | |
71 | it or regenerate `configure' using a newer version of `autoconf'. | |
72 | ||
73 | ||
4b13b216 | 74 | Building the GRUB |
6a161fa9 | 75 | ================= |
76 | ||
77 | The simplest way to compile this package is: | |
78 | ||
9f73ebd4 VS |
79 | 1. `cd' to the directory containing the package's source code. |
80 | ||
81 | 2. Skip this and following step if you use release tarball and proceed to | |
82 | step 4. If you want translations type `./linguas.sh'. | |
83 | ||
84 | 3. Type `./autogen.sh'. | |
85 | ||
86 | 4. Type `./configure' to configure the package for your system. | |
86e5b1db | 87 | If you're using `csh' on an old version of System V, you might |
88 | need to type `sh ./configure' instead to prevent `csh' from trying | |
89 | to execute `configure' itself. | |
6a161fa9 | 90 | |
91 | Running `configure' takes awhile. While running, it prints some | |
92 | messages telling which features it is checking for. | |
93 | ||
9f73ebd4 | 94 | 6. Type `make' to compile the package. |
6a161fa9 | 95 | |
9f73ebd4 | 96 | 7. Optionally, type `make check' to run any self-tests that come with |
6a161fa9 | 97 | the package. |
98 | ||
9f73ebd4 | 99 | 8. Type `make install' to install the programs and any data files and |
6a161fa9 | 100 | documentation. |
101 | ||
9f73ebd4 | 102 | 9. You can remove the program binaries and object files from the |
6a161fa9 | 103 | source code directory by typing `make clean'. To also remove the |
104 | files that `configure' created (so you can compile the package for | |
105 | a different kind of computer), type `make distclean'. There is | |
106 | also a `make maintainer-clean' target, but that is intended mainly | |
107 | for the package's developers. If you use it, you may have to get | |
108 | all sorts of other programs in order to regenerate files that came | |
109 | with the distribution. | |
110 | ||
fc97214f VS |
111 | Cross-compiling the GRUB |
112 | ======================== | |
113 | ||
114 | GRUB defines 3 platforms: | |
115 | ||
116 | - "Build" is the one which build systems runs on. | |
117 | - "Host" is where you execute GRUB utils. | |
118 | - "Target" is where GRUB itself runs. | |
119 | ||
120 | For grub-emu host and target must be the same but may differ from build. | |
121 | ||
122 | If build and host are different make check isn't available. | |
123 | ||
7f68269a VS |
124 | If build and host are different man pages are not generated. |
125 | ||
fc97214f VS |
126 | As an example imagine you have a build system running on FreeBSD on sparc |
127 | which prepares packages for developpers running amd64 GNU/Linux laptop and | |
128 | they need to make images for ARM board running U-boot. In this case: | |
129 | ||
130 | build=sparc64-freebsd | |
131 | host=amd64-linux-gnu | |
132 | target=arm-uboot | |
133 | ||
134 | For this example the configure line might look like (more details below) | |
135 | (some options are optional and included here for completeness but some rarely | |
136 | used options are omited): | |
137 | ||
138 | ./configure BUILD_CC=gcc BUILD_FREETYPE=freetype-config --host=amd64-linux-gnu | |
139 | CC=amd64-linux-gnu-gcc CFLAGS="-g -O2" FREETYPE=amd64-linux-gnu-freetype-config | |
140 | --target=arm --with-platform=uboot TARGET_CC=arm-elf-gcc | |
141 | TARGET_CFLAGS="-Os -march=armv6" TARGET_CCASFLAGS="-march=armv6" | |
142 | TARGET_OBJCOPY="arm-elf-objcopy" TARGET_STRIP="arm-elf-strip" | |
0e8daad0 | 143 | TARGET_NM=arm-elf-nm TARGET_RANLIB=arm-elf-ranlib LEX=gflex |
fc97214f VS |
144 | |
145 | You need to use following options to specify tools and platforms. For minimum | |
146 | version look at prerequisites. All tools not mentioned in this section under | |
147 | corresponding platform are not needed for the platform in question. | |
148 | ||
149 | - For build | |
150 | 1. BUILD_CC= to gcc able to compile for build. This is used, for | |
151 | example, to compile build-gentrigtables which is then run to | |
152 | generate sin and cos tables. | |
153 | 2. BUILD_CFLAGS= for C options for build. | |
154 | 3. BUILD_CPPFLAGS= for C preprocessor options for build. | |
155 | 4. BUILD_FREETYPE= for freetype-config for build (optional). | |
156 | ||
157 | - For host | |
158 | 1. --host= to autoconf name of host. | |
159 | 2. CC= for gcc able to compile for host | |
160 | 3. CFLAGS= for C options for host. | |
161 | 4. CPPFLAGS= for C preprocessor options for host. | |
162 | 5. LDFLAGS= for linker options for host. | |
163 | 6. FREETYPE= for freetype-config for host (optional). | |
164 | 7. Libdevmapper if any must be in standard linker folders (-ldevmapper) (optional). | |
165 | 8. Libfuse if any must be in standard linker folders (-lfuse) (optional). | |
166 | 9. Libzfs if any must be in standard linker folders (-lzfs) (optional). | |
167 | 10. Liblzma if any must be in standard linker folders (-llzma) (optional). | |
168 | ||
169 | - For target | |
170 | 1. --target= to autoconf cpu name of target. | |
171 | 2. --with-platform to choose firmware. | |
172 | 3. TARGET_CC= for gcc able to compile for target | |
173 | 4. TARGET_CFLAGS= for C options for target. | |
174 | 5. TARGET_CPPFLAGS= for C preprocessor options for target. | |
175 | 6. TARGET_CCASFLAGS= for assembler options for target. | |
176 | 7. TARGET_LDFLAGS= for linker options for target. | |
177 | 8. TARGET_OBJCOPY= for objcopy for target. | |
178 | 9. TARGET_STRIP= for strip for target. | |
179 | 10. TARGET_NM= for nm for target. | |
0e8daad0 | 180 | 11. TARGET_RANLIB= for ranlib for target. |
fc97214f VS |
181 | |
182 | - Additionally for emu, for host and target. | |
183 | 1. SDL is looked for in stadard linker directories (-lSDL) (optional) | |
184 | 2. libpciaccess is looked for in stadard linker directories (-lpciaccess) (optional) | |
185 | 3. libusb is looked for in stadard linker directories (-lusb) (optional) | |
186 | ||
187 | - Platform-agnostic tools and data. | |
188 | 1. make is the tool you execute after ./configure. | |
189 | 2. Bison is specified in YACC= variable | |
190 | 3. Flex is specified in LEX= variable | |
191 | 4. GNU unifont and Djvu sans are looked for in standard directories. | |
6a161fa9 | 192 | |
193 | Compiling For Multiple Architectures | |
194 | ==================================== | |
195 | ||
196 | You can compile the package for more than one kind of computer at the | |
197 | same time, by placing the object files for each architecture in their | |
198 | own directory. `cd' to the directory where you want the object files | |
199 | and executables to go and run the `configure' script. `configure' | |
200 | automatically checks for the source code in the directory that | |
201 | `configure' is in and in `..'. | |
202 | ||
203 | ||
204 | Installation Names | |
205 | ================== | |
206 | ||
207 | By default, `make install' will install the package's files in | |
208 | `/usr/local/bin', `/usr/local/man', etc. You can specify an | |
209 | installation prefix by giving `configure' the option `--prefix=PATH'. | |
210 | ||
211 | You can specify separate installation prefixes for | |
212 | architecture-specific files and architecture-independent files. If | |
213 | you give `configure' the option `--exec-prefix=PATH', the package will | |
214 | use PATH as the prefix for installing programs and libraries. | |
215 | Documentation and other data files will still use the regular prefix. | |
216 | ||
217 | In addition, if you use an unusual directory layout you can give | |
218 | options like `--bindir=PATH' to specify different values for | |
219 | particular kinds of files. Run `configure --help' for a list of the | |
220 | directories you can set and what kinds of files go in them. | |
221 | ||
222 | If the package supports it, you can cause programs to be installed | |
223 | with an extra prefix or suffix on their names by giving `configure' | |
224 | the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | |
225 | ||
4b13b216 | 226 | Please note, however, that the GRUB knows where it is located in the |
6a161fa9 | 227 | filesystem. If you have installed it in an unusual location, the |
228 | system might not work properly, or at all. The chief utility of these | |
4b13b216 | 229 | options for the GRUB is to allow you to "install" in some alternate |
6a161fa9 | 230 | location, and then copy these to the actual root filesystem later. |
231 | ||
232 | ||
233 | Sharing Defaults | |
234 | ================ | |
235 | ||
236 | If you want to set default values for `configure' scripts to share, | |
237 | you can create a site shell script called `config.site' that gives | |
238 | default values for variables like `CC', `cache_file', and `prefix'. | |
239 | `configure' looks for `PREFIX/share/config.site' if it exists, then | |
240 | `PREFIX/etc/config.site' if it exists. Or, you can set the | |
241 | `CONFIG_SITE' environment variable to the location of the site script. | |
242 | A warning: not all `configure' scripts look for a site script. | |
243 | ||
244 | ||
245 | Operation Controls | |
246 | ================== | |
247 | ||
248 | `configure' recognizes the following options to control how it | |
249 | operates. | |
250 | ||
251 | `--cache-file=FILE' | |
252 | Use and save the results of the tests in FILE instead of | |
253 | `./config.cache'. Set FILE to `/dev/null' to disable caching, for | |
254 | debugging `configure'. | |
255 | ||
256 | `--help' | |
257 | Print a summary of the options to `configure', and exit. | |
258 | ||
259 | `--quiet' | |
260 | `--silent' | |
261 | `-q' | |
262 | Do not print messages saying which checks are being made. | |
263 | ||
264 | `--srcdir=DIR' | |
265 | Look for the package's source code in directory DIR. Usually | |
266 | `configure' can determine that directory automatically. | |
267 | ||
268 | `--version' | |
269 | Print the version of Autoconf used to generate the `configure' | |
270 | script, and exit. |