From 7ff25fd1932471a23827ef821be97fc4969910e1 Mon Sep 17 00:00:00 2001
From: Francis Rowe
+ If you have the binary release archive, you'll find executables under ./bucts/. Otherwise if you need to build from source, continue reading. +
First, install the build dependencies.
@@ -150,6 +154,12 @@
Flashrom source code is included in libreboot_src.tar.gz and libreboot_bin.tar.gz.
If you downloaded from git, follow #build_meta before you proceed.
+ If you are using the binary release archive, then there are already binaries included + under ./bin/. The flashing scripts will try to choose the correct one for you. Otherwise + if you wish to re-build flashrom from source, continue reading. +
First, install the build dependencies. @@ -422,6 +432,13 @@
You don't need to do much, as there are scripts already written for you that can build everything automatically.
+ You can build libreboot from source on a 32-bit (i686) or 64-bit (x86_64) system. Recommended (if possible): x86_64. + On a ThinkPad T60, you can replace the CPU (Core 2 Duo T5600, T7200 or T7600. T5600 recommended) for 64-bit support. + On an X60s, you can replace the board with one that has a Core 2 Duo L7400 (you could also use an X60 Tablet board with the same CPU). + On an X60, you can replace the board with one that has a Core 2 Duo T5600 or T7200 (T5600 is recommended). +
+ +First, install the build dependencies.
@@ -453,6 +470,22 @@
+ If you are building on an i686 host, this will include statically linked 32-bit binaries in the binary release archive that you created, + for: nvramtool, cbfstool, bucts, flashrom. +
+ ++ If you are building on an x86_64 host, this will include statically linked 32- and 64-bit binaries for cbfstool and nvramtool, while flashrom + and bucts will be included only as 64-bit statically linked binaries. To include a statically linked flashrom and bucts for i686, you + will need to build them on a chroot, a virtual machine or a real 32-bit system. You can find the build dependencies for these packages listed in deps-* +
+ +
+ If you are building 32-bit binaries on a live system or chroot (for flashrom/bucts), you can use the following to statically link them:
+ $ make SHARED=0 CC='gcc -static'
+
You'll find that the files libreboot_bin.tar.xz and libreboot_src.tar.xz have been created.
@@ -479,8 +512,8 @@
- Build cbfstool:
- $ ./builddeps-cbfstool
+ Binaries for cbfstool are provided (built from libreboot_src) statically linked under cbfstool/ and the addseabios
+ script (see below) will try to automatically select the right one to use.
diff --git a/docs/gnulinux/grub_cbfs.html b/docs/gnulinux/grub_cbfs.html index 63b9551..8b5a8a6 100644 --- a/docs/gnulinux/grub_cbfs.html +++ b/docs/gnulinux/grub_cbfs.html @@ -90,9 +90,7 @@ executable.
- Alternatively if you are working with libreboot_bin, then you can run ./builddeps-cbfstool - command inside libreboot_bin/; a cbfstool and rmodtool - executable will appear under libreboot_bin/ + Alternatively if you are working with libreboot_bin, you will find binaries under ./cbfstool/
-- cgit v0.9.1