eudev instructions refering to /tools

[thomas]

As far as i can remember, eudev was not always the very last package in chapter 6. At this time it might be the case that not everything needed by eudev was installed already. But now, as it is now the last package, everything needed must be installed, otherwise it would mean that chapter 6 is incomplete. When everything is installed, i see no need to specify LD_LIBRARY_PATH=/tools/lib compiling that package. I think that is simply remainder of when eudev was build before core-utils or such...

Index: chapter06/eudev.xml
===================================================================
--- chapter06/eudev.xml	(revision 11613)
+++ chapter06/eudev.xml	(working copy)
@@ -49,15 +49,7 @@
 
 <screen><userinput remap="pre">sed -i '/keyboard_lookup_key/d' src/udev/udev-builtin-keyboard.c</userinput></screen>
 -->
-    <para>First, add a workaround to prevent the /tools directory from being 
-    hard coded into Eudev binary files library locations:</para>
 
-<screen><userinput remap="pre">cat &gt; config.cache &lt;&lt; "EOF"
-HAVE_BLKID=1
-BLKID_LIBS="-lblkid"
-BLKID_CFLAGS="-I/tools/include"
-EOF</userinput></screen>
-
 <para>Prepare Eudev for compilation:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/usr           \
@@ -69,19 +61,10 @@
             --with-rootprefix=      \
             --with-rootlibdir=/lib  \
             --enable-manpages       \
-            --disable-static        \
-            --config-cache</userinput></screen>
+            --disable-static</userinput></screen>
 
 <para>Compile the package:</para>
 
-<screen><userinput remap="make">LIBRARY_PATH=/tools/lib make</userinput></screen>
-
-<note><para>The LIBRARY_PATH variable here and the LD_LIBRARY_PATH variable
-below are needed to allow the use of libraries that were installed in /tools,
-but have not yet been installed in the main system.  LIBRARY_PATH is
-used to find libraries during the linking process.  LD_LIBRARY_PATH is
-used to find libraries during program execution.</para></note>
-
 <para>Create some directories now that are needed for tests, but
 will also be used as a part of installation:</para>
 
@@ -90,11 +73,11 @@
 
 <para>To test the results, issue:</para>
 
-<screen><userinput remap="test">make LD_LIBRARY_PATH=/tools/lib check</userinput></screen>
+<screen><userinput remap="test">make check</userinput></screen>
 
     <para>Install the package:</para>
 
-<screen><userinput remap="install">make LD_LIBRARY_PATH=/tools/lib install</userinput></screen>
+<screen><userinput remap="install">make install</userinput></screen>
 
     <para>Install some custom rules and support files useful in an LFS 
     environment:</para>
@@ -123,7 +106,7 @@
     into a binary database <filename>/etc/udev/hwdb.bin</filename>. Create the
     initial database:</para>
 
-<screen><userinput>LD_LIBRARY_PATH=/tools/lib udevadm hwdb --update</userinput></screen>
+<screen><userinput>udevadm hwdb --update</userinput></screen>
 
     <para>This command needs to be run each time the hardware information is
     updated.</para>

Thoughts?

[Bruce Dubbs]

We can probably do that. I moved eudev to the end of Chapter 6 because I wanted to keep all the sysv/systemd specific packages at the end. This means that most of Chapter 6 is generic for both types of builds.

The move does mean that /tools is no longer necessary. I'll get this at the next LFS update.

[Bruce Dubbs]

Fixed at revision 11619.

[Bruce Dubbs]

Milestone renamed