Gentoo Archives: gentoo-user

From: Pandu Poluan <pandu@××××××.info>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails
Date: Wed, 23 May 2012 09:05:17
Message-Id: CAA2qdGX6L3nVz9EmFh7UDjFqSWfXTBJ7yO+=yOAQSNMGa7nRqw@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails by Michael Scherer
1 On May 23, 2012 9:14 AM, "Michael Scherer" <a6702894@××××××××××××××.at>
2 wrote:
3 >
4 > On Thu, 17 May 2012 22:59:41 +0200
5 > Alex Schuster <wonko@×××××××××.org> wrote:
6 >
7 > > Michael Scherer writes:
8 > >
9 > > > 1) make output:
10 > > >
11 > > > CHK include/linux/version.h
12 > > > CHK include/generated/utsrelease.h
13 > > > CALL scripts/checksyscalls.sh
14 > > > CHK include/generated/compile.h
15 > > > LD init/mounts.o
16 > > > ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
17 > > > init/do_mounts_initrd.o init/mounts.o: No such file or directory
18 > > > make[1]: *** [init/mounts.o] Error 1
19 > > > make: *** [init] Error 2
20 > > >
21 > > > There is an LD, the ls line is part of the error message.
22 > >
23 > > But the options look really more like ld options to me. How this could
24 > > possibly happen, I don't know. Some overriding of $(LD) perhaps? Does
25 > > "env | egrep -i 'ls|ld'" show something weird? Does it also fail as a
26 > > non-root user, after you copied the stuff over to somewhere where this
27 > > user can write? Just grasping at straws here.
28 > >
29 > >
30 > > > But without doubt you are right that mounts.o is not built, for
31 > > > whatever reason.
32 > >
33 > > Because ld should build it from init/do_mounts.o, but ls is being
34 > > called instead?
35 > >
36 > > > The build command
37 > > >
38 > > > init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
39 > > > -Wp,-MD,init/.do_mounts.o.d -nostdinc
40 > > > -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
41 > > > -I/usr/src/linux-3.2.12-gentoo/arch/x86/include
42 > > > -Iarch/x86/include/generated -Iinclude
43 > > > -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
44 > > > -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
45 > > > -fno-strict-aliasing -fno-common
46 > > > -Werror-implicit-function-declaration -Wno-format-security
47 > > > -fno-delete-null-pointer-checks -O2 -m64 -march=k8 -mno-red-zone
48 > > > -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
49 > > > -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
50 > > > -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe
51 > > > -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx
52 > > > -mno-sse2 -mno-3dnow -Wframe-larger-than=2048
53 > > > -fno-omit-frame-pointer -fno-optimize-sibling-calls
54 > > > -fno-inline-functions-called-once -Wdeclaration-after-statement
55 > > > -Wno-pointer-sign -fno-strict-overflow -fconserve-stack
56 > > > -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
57 > > > -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
58 > > > -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
59 > > > init/do_mounts.c
60 > > >
61 > > > contains a directive to build mounts.o, see second last line, but
62 > > > it for some reason this is ignored.
63 > > > Maybe there is a flaw in that command, only I can't find it.
64 > >
65 > > Neither can I. Is this command executed at all? If you maybe replace
66 > > the 'gcc' by 'gccXXX', does this give an error? Or put an 'echo' in
67 > > front of the gcc'.
68 > > You can try 'make -d', this will give you LOTS of debug output, but I
69 > > don't think you will see the actual commands then.
70 > >
71 > > Wonko
72 > >
73 >
74 > Now at last there is some kind of "progress". Last thing I tried was
75 > replacing my current .config with that of my previous kernel (3.2.1-r2)
76 > and at least the make ran all the way up to the point where it should
77 > link everything to build vmlinux, only now it tells me it couldn't
78 > find vmlinux.o.
79 >
80 > The last couple of lines from the make output:
81 >
82 > CC arch/x86/lib/cache-smp.o
83 > CC arch/x86/lib/msr.o
84 > AS arch/x86/lib/msr-reg.o
85 > CC arch/x86/lib/msr-reg-export.o
86 > AS arch/x86/lib/iomap_copy_64.o
87 > LD arch/x86/lib/built-in.o
88 > ls -Al -m elf_x86_64 -r -o arch/x86/lib/built-in.o
89 > arch/x86/lib/msr-smp.o arch/x86/lib/cache-smp.o arch/x86/lib/msr.o
90 > arch/x86/lib/msr-reg.o arch/x86/lib/msr-reg-export.o
91 > arch/x86/lib/iomap_copy_64.o
92 > AS arch/x86/lib/clear_page_64.o
93 > AS arch/x86/lib/cmpxchg16b_emu.o
94 > AS arch/x86/lib/copy_page_64.o
95 > AS arch/x86/lib/copy_user_64.o
96 > AS arch/x86/lib/copy_user_nocache_64.o
97 > AS arch/x86/lib/csum-copy_64.o
98 > CC arch/x86/lib/csum-partial_64.o
99 > CC arch/x86/lib/csum-wrappers_64.o
100 > CC arch/x86/lib/delay.o
101 > AS arch/x86/lib/getuser.o
102 > GEN arch/x86/lib/inat-tables.c
103 > CC arch/x86/lib/inat.o
104 > CC arch/x86/lib/insn.o
105 > AS arch/x86/lib/memcpy_64.o
106 > AS arch/x86/lib/memmove_64.o
107 > AS arch/x86/lib/memset_64.o
108 > AS arch/x86/lib/putuser.o
109 > AS arch/x86/lib/rwlock.o
110 > AS arch/x86/lib/rwsem.o
111 > AS arch/x86/lib/thunk_64.o
112 > CC arch/x86/lib/usercopy.o
113 > CC arch/x86/lib/usercopy_64.o
114 > AR arch/x86/lib/lib.a
115 > LD vmlinux.o
116 > ls -Al -m elf_x86_64 -r -o vmlinux.o arch/x86/kernel/head_64.o
117 > arch/x86/kernel/head64.o arch/x86/kernel/head.o
118 > arch/x86/kernel/init_task.o init/built-in.o --start-group
119 > usr/built-in.o arch/x86/built-in.o kernel/built-in.o mm/built-in.o
120 > fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o
121 > block/built-in.o lib/lib.a arch/x86/lib/lib.a lib/built-in.o
122 > arch/x86/lib/built-in.o drivers/built-in.o sound/built-in.o
123 > firmware/built-in.o arch/x86/pci/built-in.o arch/x86/power/built-in.o
124 > arch/x86/video/built-in.o net/built-in.o --end-group
125 > MODPOST vmlinux.o
126 > vmlinux.o: No such file or directory make[1]: ***
127 > [vmlinux.o] Error 1 make: *** [vmlinux.o] Error 2
128 >
129 >
130 > Essentially the same error as previously with mounts.o, and after
131 > every LD comes an ls -Al ... line like above, which I never saw
132 > before in my make outputs. Don't know where that comes from.
133 >
134 > I'm now back where the troubles began, the vmlinux.o error was
135 > the first I encountered after my last successful build.
136 > Maybe a careful search of a diff of the .config files will
137 > give me some idea.
138 >
139 > By now you're probably somewhat tired of devoting your time
140 > to this problem, so thank you for all your efforts to help me.
141 > If I ever solve this, you'll hear from me (which doesn't mean
142 > the thread is closed. If someone is still curious... ;-) )
143 >
144 > Kind regards, Michael
145 >
146
147 If the problem is due to .config, run make oldconfig first.
148
149 Rgds,