|
From: <gd...@tx...> - 2011-03-29 18:24:31
|
Hi,
While attempting to build Devil-Linux 1.4.1 I came across several build problems. Three of them are just
minor annoyances but #1 is a show stopper. I am running the build on Debian Lenny (32 bit) installed
in /usr/src/lfssystem. I was previously able to successfully build 1.2 on Debian Etch also installed in
/usr/src/lfssystem. The 1.2 build system was deleted before 1.4.1 was installed. I am about to install
1.4.2 but I want to make sure that this (#1) is not an install problem before I do.
1) Running make prepare from (chroot) /build as root I get:
root:/build# make prepare
mount: proc already mounted
mount: mount point /sys does not exist
make: Entering directory `/build'
prepare: prepare log: /build/tmp/LOGS/prepare/prepare
make: *** [prepare] Error 1
make: Leaving directory `/build'
make: *** [prepare] Error 1
root:/build#
In /build/tmp/LOGS/prepare/prepare:
+ '[' -d /usr/src/linux ']'
+ '[' '!' -L /usr/src/linux ']'
+ pushd /build/tmp/linux-2.6.32
+ '[' '!' -f .minor_version_patch.done ']'
+ fake_systemtype
+ '[' -n 2.6.32 ']'
+ test -f /bin/uname.old
+ rm /bin/uname
++ /bin/uname.old -r
+ REALKERNEL=2.6.26-2-686
+ echo '/bin/uname.old $* | sed -e '\''s/i.86/i686/g'\'' | sed -e '\''s/x86_64/i686/g'\'' | sed -e \
'\''s/athlon-./i686/g'\'' | sed -e '\''s/athlon/i686/g'\'' | sed -e '\''s/2.6.26-2-686/2.6.32/g'\'''
+ chmod +x /bin/uname
+ test -f /bin/arch.old
+ echo '/bin/uname -m'
++ find_src_dir kernel-includes
+++ ls -d '/build/tmp/kernel-includes[-_][0123456789]*'
++ SDIR=
++ '[' -z '' ']'
+++ ls -d '/build/tmp/kernel-includes*'
++ SDIR=
++ echo
+ KERN_INC=
+ ln -sf /build/tmp/linux-2.6.32 /usr/src/linux
+ make -C /build/tmp/linux-2.6.32 headers_check
make: Entering directory `/build/tmp/linux-2.6.32'
CHK include/linux/version.h
HOSTCC scripts/basic/fixdep
In file included from /usr/include/bits/posix1_lim.h:126,
from /usr/include/limits.h:144,
from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/limits.h:122,
from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/syslimits.h:7,
from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/include/limits.h:11,
from scripts/basic/fixdep.c:114:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
In file included from /usr/include/netinet/in.h:212,
from /usr/include/arpa/inet.h:23,
from scripts/basic/fixdep.c:116:
/usr/include/bits/socket.h:305:24: asm/socket.h: No such file or directory
scripts/basic/fixdep.c: In function `use_config':
scripts/basic/fixdep.c:204: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:204: error: (Each undeclared identifier is reported only once
scripts/basic/fixdep.c:204: error: for each function it appears in.)
scripts/basic/fixdep.c:204: warning: unused variable `s'
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:304: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:304: warning: unused variable `s'
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2
make: Leaving directory `/build/tmp/linux-2.6.32'
+ exit 1
After looking around I found these three links in (chroot) /usr/include:
lrwxrwxrwx 1 root root 39 Oct 2 15:26 linux -> /build/tmp/linux-2.4.36.6/include/linux
lrwxrwxrwx 1 root root 42 Oct 2 15:26 asm -> /build/tmp/linux-2.4.36.6/include/asm-i386
lrwxrwxrwx 1 root root 45 Oct 2 15:26 asm-generic -> /build/tmp/linux-2.4.36.6/include/asm-generic
At this point I don't know if changing these links to /build/tmp/linux-2.6.32/include/... will fix it or
if there is a bigger problem with the install (there is no /build/tmp/linux-2.6.32/include/asm-i386
directory) or configuration (CONFIG_LINUX_VERSION is set to 2.6). I looked through the discuss mailing
list and there were no previous entries about this so I seem to be the only one seeing this. Any ideas
as to what I am doing wrong ?
2) After exiting any menu in make menuconfig I get this error:
/build/tmp/.config: cd: /build/tmp/.config: Not a directory
After exiting, menuconfig says that the changes were saved and the .config file in the /build directory
seems to be correct so this appears to be just annoying. I have spent a little time looking for where
this message is being sent from so far with no success.
3) In the chroot /root/.bash_profile why is it cd /build/data instead of cd /build ?
4) grep did not find update_md5sum in any of the html documentation files or the update_src script. Since I
got md5sum error messages when I ran update_src I assume that update_md5sum should be run before running
update_src?
Thanks,
Gary Stewart
|