Summary: | dev-util/oprofile-1.1.0-r1 : * ERROR: dev-util/oprofile-1.1.0-r1::gentoo failed (setup phase): | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Andrew Savchenko <bircoph> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-util:oprofile-1.1.0-r1:20160603-043053.log
die.env emerge-history.txt |
Description
Toralf Förster
![]() Created attachment 436272 [details]
dev-util:oprofile-1.1.0-r1:20160603-043053.log
Created attachment 436274 [details]
die.env
Created attachment 436276 [details]
emerge-history.txt
Hi, I can't reproduce this issue. Do you have a valid /usr/src/linux/.config file? If not, probably you should setup your thinderbox to generate one, e.g. using genkernel or make defconfig. The problem is , that that package did not even pulled in sources before - the sources came in later at this image : ms-magpie / # qlop -u -l gentoo-sources Fri Jun 3 14:22:00 2016 >>> sys-kernel/gentoo-sources-4.4.6 IIRC there were similar things in the past and an eclass seems to be the culprit (despite the fact, that pulling in sources wouldn't configure them). Hello, I'm not really sure that eclass must pull sources: there are numerous ways to configure, build and install kernel, many of them are out-of-the-tree. And even if sources are installed, it is always user's job to configure them properly, eclass or ebuild can't and shouldn't do that. If system is running in LXC container, sources are not needed at all: it is sufficient to provide .config of the running kernel. As far as oprofile is concerned, this bug is invalid, because kernel on thinderbox is not properly configured. I see two ways to fix this: 1. make defconfig. Easy, but some packages will not work properly if some CONFIG_ options are not configured the way they want or if they are different from how running kernel was configured; 2. supply your thinderbox's kernel config, this is probably the best way. If you think that linux-info.eclass must pull gentoo-sources, please report this to eclass maintainers (kernel@g.o). |