Bug 10111 - Kernel headers error
Summary: Kernel headers error
Status: CLOSED CODE_FIX
Alias: None
Product: Other
Classification: Unclassified
Component: Configuration (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Roman Zippel
URL:
Keywords:
: if_addrlabel.h (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-02-26 01:27 UTC by simone nanni
Modified: 2008-05-15 14:19 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.24.3
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
My .config file (29.80 KB, application/xml)
2008-02-26 01:39 UTC, simone nanni 		Details
Add an attachment (proposed patch, testcase, etc.)

Description simone nanni 2008-02-26 01:27:24 UTC 
Latest working kernel version: 2.6.24.2

Earliest failing kernel version: 2.6.24.2

Distribution: Slamd 64

Hardware Environment: 2 Opteron 850, 4GB RAM, 72GB SCSI HDD RAID1

Software Environment: Postfix, MySQL 5.0.51a, Apache 2.2.8, PHP 5.2.5, Courier-IMAP

Problem Description:
make[3]: *** No rule to make target `/usr/src/linux-2.6.24.3/include/linux/if_addrlabel.h', needed by `/usr/src/linux-2.6.24.3/usr/include/linux/if_addrlabel.h'.  Stop.
make[2]: *** [linux] Error 2
make[1]: *** [headers_install] Error 2
make: *** [vmlinux] Error 2

Steps to reproduce:
Comment 1 simone nanni 2008-02-26 01:39:20 UTC 
Created attachment 15003 [details]
My .config file
Comment 2 simone nanni 2008-02-26 01:44:38 UTC 
I use GCC 3.4.6
Comment 3 Adrian Bunk 2008-02-26 08:51:23 UTC 
Known bug (will most likely be fixed in 2.6.24.4).
Comment 4 Adrian Bunk 2008-02-26 08:52:48 UTC 
*** Bug 10113 has been marked as a duplicate of this bug. ***
Comment 5 Roland Kletzing 2008-05-15 12:14:00 UTC 
should be fixed in stable:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.24.y.git;a=commit;h=5c2699a0d511a78ae8692ab08f4a332a634b0d67

can you confirm ?
Comment 6 Anonymous Emailer 2008-05-15 14:55:00 UTC 
Reply-To: pavel@pavlinux.ru

В сообщении от Thursday 15 May 2008 23:14:00 вы написали:
> can you confirm ?

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