Custom Query (532 matches)

In kernel 2.6.38 (and maybe others, haven't checked), a value of "mipsel" isn't valid for the way we use it in the Linux headers installation. The value needs to be "mips" for all variants of mips target triplets.

The offending sed line is:

export CLFS_ARCH=$(echo ${CLFS_TARGET} | sed -e 's/\(mips\)\(64\)\?\(el\)\?-.*/\1\3/')

Could changing this to just be "mips" rather than a possible "mipsel" be bad in other places in the book?

${CLFS}/usr/include is created in the embedded book in section 4.4 but is then created again in section 6.5. It's not required to create it twice as in both cases the permissions are the same.

I had some oddities with modprobe not working in the final system, or only working sometimes - tracked that to whether /tools existed, found that modprobe was liked against tools. Also discovered that if I reinstalled after booting the final system, it didn't overwrite the old modprobe so I had to delete that.

Steps to reproduce: follow the 'boot' method, or at least build and install module-init-tools from chapter 7. In the final system, review the module programs.

Here are the results of 'ls -l' and 'ldd /sbin/*mod*' on a current multilib build, halted after installing modprobe in the final system:

-rwxr-xr-x 1 root root  153412 May 17 21:12 /sbin/depmod
-rwxr-xr-x 1 root root    8723 Jun  9 03:43 /sbin/generate-modprobe.conf
-rwxr-xr-x 1 root root   24668 May 17 21:12 /sbin/insmod
-rwxr-xr-x 1 root root 3159745 Jun  9 03:43 /sbin/insmod.static
lrwxrwxrwx 1 root root      12 Jun  9 03:43 /sbin/lsmod -> ../bin/lsmod
-rwxr-xr-x 1 root root  137646 Jun  9 03:43 /sbin/modinfo
-rwxr-xr-x 1 root root  109890 May 17 21:12 /sbin/modprobe
-rwxr-xr-x 1 root root   35474 May 17 21:12 /sbin/rmmod
/sbin/depmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/generate-modprobe.conf:
        not a dynamic executable
/sbin/insmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/insmod.static:
        not a dynamic executable
/sbin/lsmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libc.so.6 => /lib64/libc.so.6 (0x0000040000038000)
        /lib64/ld64.so.1 (0x0000040000000000)
/sbin/modinfo:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libc.so.6 => /lib64/libc.so.6 (0x0000040000038000)
        /lib64/ld64.so.1 (0x0000040000000000)
/sbin/modprobe:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)
/sbin/rmmod:
        linux-vdso64.so.1 =>  (0x0000000000100000)
        libgcc_s.so.1 => /tools/lib64/libgcc_s.so.1 (0x0000040000038000)
        libc.so.6 => /tools/lib64/libc.so.6 (0x000004000005b000)
        /tools/lib64/ld64.so.1 (0x0000040000000000)

So, insmod.static, lsmod, modinfo are the correct versions but depmod, insmod, modprobe, rmmod are the temporary versions linked against /tools.

Suggested solution: rm -rf /sbin/depmod /sbin/insmod /sbin/modprobe /sbin/rmmod before running 'make install' in chapter 10.