Bug 32622 - linux 2.6.39-rc1 does not build
Summary: linux 2.6.39-rc1 does not build
Status: RESOLVED INVALID
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 07:28 UTC by Michal Suchanek
Modified: 2011-04-04 22:13 UTC (History)
1 user (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:

Attachments
kernel config (113.10 KB, text/plain)
2011-04-04 07:28 UTC, Michal Suchanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Michal Suchanek 2011-04-04 07:28:11 UTC 
Created attachment 53432 [details]
kernel config

I could not build kernel head with my patches a few days ago.

I tried to check out the clean rc1 and the problem persists:

/usr/bin/make  EXTRAVERSION=-rc1-amd64  ARCH=x86_64 \
                             bzImage
make[1]: Entering directory `/scratch/um/linux-2.6'
scripts/kconfig/conf --silentoldconfig Kconfig
make[1]: Leaving directory `/scratch/um/linux-2.6'
make[1]: Entering directory `/scratch/um/linux-2.6'
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  CC      init/version.o
  LD      init/built-in.o
  CC      kernel/trace/trace.o
  LD      kernel/trace/built-in.o
  CC      kernel/module.o
  CC      kernel/kexec.o
  LD      kernel/built-in.o
  CC      arch/x86/lib/memmove_64.o
gcc: arch/x86/lib/memmove_64.c: No such file or directory
gcc: no input files
Comment 1 Randy Dunlap 2011-04-04 16:34:02 UTC 
I'm not having any build errors when using your kernel config file.
memmove_64.S (not .c) is present and is built with AS:
  AS      arch/x86/lib/memmove_64.o

What do your patches do?
Comment 2 Michal Suchanek 2011-04-04 17:07:20 UTC 
Nothing, I did not apply them to the tree.
Comment 3 Michal Suchanek 2011-04-04 22:09:42 UTC 
Clean build works.
Obviously I had some leftovers from my 2.6.37 build which caused this.
Note You need to log in before you can comment on or make changes to this bug.