1 |
On Thu, May 17, 2012 at 4:50 PM, Hinnerk van Bruinehsen |
2 |
<h.v.bruinehsen@×××××××××.de> wrote: |
3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
4 |
> Hash: SHA1 |
5 |
> |
6 |
> On 17.05.2012 22:13, Michael Scherer wrote: |
7 |
> |
8 |
>> |
9 |
>> 1) make output: |
10 |
>> |
11 |
>> CHK include/linux/version.h CHK |
12 |
>> include/generated/utsrelease.h CALL scripts/checksyscalls.sh CHK |
13 |
>> include/generated/compile.h LD init/mounts.o ls -Al -m |
14 |
>> elf_x86_64 -r -o init/mounts.o init/do_mounts.o |
15 |
>> init/do_mounts_initrd.o init/mounts.o: No such file or directory |
16 |
>> make[1]: *** [init/mounts.o] Error 1 make: *** [init] Error 2 |
17 |
>> |
18 |
>> There is an LD, the ls line is part of the error message. |
19 |
>> |
20 |
> |
21 |
>> |
22 |
>> contains a directive to build mounts.o, see second last line, but |
23 |
>> it for some reason this is ignored. Maybe there is a flaw in that |
24 |
>> command, only I can't find it. |
25 |
>> |
26 |
>> regards, michael |
27 |
>> |
28 |
>> |
29 |
> |
30 |
> Have you tried a make clean on your sourcetree? |
31 |
> |
32 |
> CHK include/linux/version.h |
33 |
> |
34 |
> IS for me one of the first lines I get at all. It seems strange to me |
35 |
> that you get a call to the linker (LD) before even a call to the |
36 |
> compiler (CC). |
37 |
> |
38 |
> I'd suggest you try a make clean first and try to build again |
39 |
> afterwards (with -j1 or without a statement for jobs) to rule out race |
40 |
> conditions. |
41 |
> |
42 |
> If that doesn't help, move your kernel sources to another directory |
43 |
> and reemerge the sources. Copy your .config (ideally one of a working |
44 |
> tree) and try again. If that doesn't help, try to get a working |
45 |
> default config (like from /proc/config.gz from a live distro). |
46 |
> |
47 |
> WKR |
48 |
> |
49 |
> Hinnerk |
50 |
> -----BEGIN PGP SIGNATURE----- |
51 |
> Version: GnuPG v2.0.19 (GNU/Linux) |
52 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
53 |
> |
54 |
> iQEcBAEBAgAGBQJPtWSXAAoJEJwwOFaNFkYc8tAH/iV59mb5MsH0pJ28dXUqe0X6 |
55 |
> tcbKB18vIQYmjG9gecGX4lVtgXCIhTqVeHEKbQVN4xRMo9u7D7FxygHtRY7sfYrk |
56 |
> dvR9fs4RfIoykVeCF/0uVSNZnoXhixarYtr8FGvIKCxvUJnY/ws4W+k5tP8Ju8lJ |
57 |
> wM5ldQ/eD8H4vFm4fIStQheTGERZlueNBVf77cLx8K/8p0XBvVM85V/epg+fC4I4 |
58 |
> bfWG1JtXrh1MUmaE+Y26aNOXGkUZiHax49CBiOUQLZNjk6f5idGppWV03HTL4mCV |
59 |
> +dI6lNaUqU0AhnoG3yIOK8lY4kFu3QmNw4h1r+OCctASMJe8dUOTnF53TjJzYQk= |
60 |
> =TguL |
61 |
> -----END PGP SIGNATURE----- |
62 |
> |
63 |
|
64 |
I'd be more active and vocal in trying to help sort this out, but it's |
65 |
been a busy week since the 1k mile trip to get a car and working on |
66 |
getting it into the shape I want it in... that aside, I *did* manage |
67 |
to, without any changes, drop in the config provided at the start of |
68 |
all this into a gentoo-sources 3.2.12 tree (after a quick mrproper) |
69 |
and it built without issues. To me, that indicates that the toolchain, |
70 |
particular copy of the sources, or hardware have an issue. That the |
71 |
problem is as consistent as it is while the rest of the system isn't |
72 |
failing in horrifying ways implies it's not the hardware. The |
73 |
resulting modules and kernel from my building it can be grabbed from |
74 |
http://poisonbl.freeshell.org/3.2.12_test.tar.bz2 |
75 |
|
76 |
-- |
77 |
Poison [BLX] |
78 |
Joshua M. Murphy |