First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 235285
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Michal Januszewski <spock@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Zeev Tarantov <zeev.tarantov@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 235285 depends on: Show dependency tree
Bug 235285 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-08-20 12:06 0000
The ebuild should verify that the kernel option CONFIG_OPROFILE is enabled ("m"
or "y"). Note it is available only when CONFIG_PROFILING=y.
The ebuild checks the version of my kernel, but not this.
Granted, there is a runtime check that tipped me off, but a warning at build
time could have saved me the hassle.

Reproducible: Always

Steps to Reproduce:
1. build oprofile on system where `grep 'CONFIG_OPROFILE=n'
/usr/src/linux/.config`
2. build succeeds.
3. opcontrol --init says it can't load module oprofile. get confused.

Actual Results:  
build succeeds.

opcontrol --init says it can't load module oprofile. get confused.


Expected Results:  
ebuild checks my kernel, warns me that I need to build this module for the
package to work. Does not prevent me from building package.

I'm using sys-kernel/gentoo-sources-2.6.26-r1 on latest ~x86, not that it
matters.

------- Comment #1 From Michal Januszewski 2008-08-20 19:09:11 0000 -------
Fixed in CVS :) Thanks for the useful suggestion.

First Last Prev Next    No search results available      Search page      Enter new bug