Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 527534 - sys-kernel/gentoo-sources-3.17.2 with USE="experimental" merges bfq scheduler sources under b/block
Summary: sys-kernel/gentoo-sources-3.17.2 with USE="experimental" merges bfq scheduler...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
: 527578 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-10-30 22:25 UTC by bwcknr
Modified: 2014-10-31 09:30 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bwcknr 2014-10-30 22:25:14 UTC
As described in summary:

# equery f gentoo-sources | grep bfq
/usr/src/linux-3.17.2-gentoo/b/block/bfq-cgroup.c
/usr/src/linux-3.17.2-gentoo/b/block/bfq-ioc.c
/usr/src/linux-3.17.2-gentoo/b/block/bfq-iosched.c
/usr/src/linux-3.17.2-gentoo/b/block/bfq-sched.c
/usr/src/linux-3.17.2-gentoo/b/block/bfq.h

This makes kernel builds fail with:
No rule to make target block/bfq-iosched.o

Reproducible: Always

Steps to Reproduce:
1. merge gentoo-sources-3.17.2 with USE="experimental"
2. try to build kernel with bfq enabled
Actual Results:  
kernel should build fine

Expected Results:  
kernel build rails
Comment 1 bwcknr 2014-10-30 22:26:43 UTC
*argh* night workers...
Actual Results:  
kernel build fails with bfq enabled

Expected Results:  
kernel builds fine
Comment 2 Mike Pagano gentoo-dev 2014-10-30 23:32:11 UTC
I fixed this, but it may take a few hours to sync to your system.

The fixed 3.17.2 ebuild has K_GENPATCHES_VER="5" in it.

you can edit your own if you like and then do

ebuild gentoo-sources-3.17.2.ebuild manifest

and then emerge it.
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2014-10-31 09:30:32 UTC
*** Bug 527578 has been marked as a duplicate of this bug. ***