Bug 140500 - linux-2.6.9-1.6_FC2] compile error
Summary: linux-2.6.9-1.6_FC2] compile error
Status: CLOSED DUPLICATE of bug 126342
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-23 04:54 UTC by Darin May
Modified: 2015-01-04 22:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-11-25 06:39:29 UTC

Attachments (Terms of Use)

Description Darin May 2004-11-23 04:54:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:
Error after a "make all" near end of compile run:

[root@localhost linux-2.6.9-1.6_FC2]# make all
  GEN     .version
  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
mm/built-in.o(.text+0x13956): In function `rw_vm':
: undefined reference to `kmap_atomic_pte'
mm/built-in.o(.text+0x13b98): In function `str_vm':
: undefined reference to `kmap_atomic_pte'
make: *** [.tmp_vmlinux1] Error 1
[root@localhost linux-2.6.9-1.6_FC2]# 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. make mrproper
2. make xconfig
3. make all

Actual Results:  see above

Expected Results:  compile ok

Additional info:

Comment 1 Dave Jones 2004-11-23 05:15:19 UTC

*** This bug has been marked as a duplicate of 126342 ***

Comment 2 Darin May 2004-11-23 23:44:36 UTC
I have narrowed this down so that it's a usefull report:

Simply use the -686 default config and go into the Processor Features
page in xconfig and disable high memory support.

Comment 3 Dave Jones 2004-11-25 06:39:29 UTC

*** This bug has been marked as a duplicate of 126342 ***

Comment 4 Darin May 2004-11-25 08:02:00 UTC
(In reply to comment #3)
> *** This bug has been marked as a duplicate of 126342 ***

Pardon me for confusing bugzilla as a bug reporting tool.

I've located a bug, generated a simple test case, and shoved into a corner.

What is the method for reporting kernel compile bugs?  it's not as though I have
an esoteric case, but a specific, detailed report.  

Are we to assume that kernel development is immune from bug reports?

Note You need to log in before you can comment on or make changes to this bug.