Summary: | nss does not compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | mike <michael.stahn.42> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
mike
2011-09-06 08:25:32 UTC
First of all, you've failed to provide the actual error. Second, you're mixing stable and unstable. Having said that, keyword a more recent nss (which is soon to be stabilized) - most likely it's the linux3.0 problem. (In reply to comment #1) Hi, > First of all, you've failed to provide the actual error. No I did not. Please re-read the first line of my report. > Second, you're mixing stable and unstable. > > Having said that, keyword a more recent nss (which is soon to be stabilized) I did not keyword dev-lib/nss. My current version (stable) is 3.12.9-r1 and I'm updating to 3.12.10 (stable). > - most likely it's the linux3.0 problem. THIS could be helpful, thanks :) :roll: Those first lines are just the portage failure message, not the actual error. (In reply to comment #3) > :roll: Those first lines are just the portage failure message, not the actual > error. pfff ^^ Well then read the 2nd line, too. It clearly says: "ERROR: ..", which cleary describes the error. It's not that hard ;) :roll: No, Pinky. The real error most likely was like in bug 372001: ../coreconf/config.mk:71: ../coreconf/Linux3.0.mk: No such file or directory Once again, the (nearly) generic portage error message is *not* the actual error. (In reply to comment #5) > :roll: No, Pinky. > The real error most likely was like in bug 372001: > ../coreconf/config.mk:71: ../coreconf/Linux3.0.mk: No such file or directory ^^ *g* Nope goofy, there is no difference between "real" and "wrong" errors. There is a chain of errors and my post was part of it, even it wasn't the starting one. > > Once again, the (nearly) generic portage error message is *not* the actual > error. It's not my job to find the first error which leads to the portage-message. I'm just posting my config and what the system tells me to find and remove the bug. I don't expect you to understand this and I wont waste any more time in this useless discussion ;) |