Summary: | kernel "make xconfig" doesn't work on qt4-only system | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James <jamespratt> |
Component: | [OLD] Library | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | bugs.gentoo.org.list, m1k0, ples349 |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Results of jakub's request. |
Description
James
2006-05-19 00:25:13 UTC
Run make clean, then 'KBUILD_VERBOSE=1 make xconfig' and attach the output here. Created attachment 87055 [details]
Results of jakub's request.
Sure thing! Here it is...
You forgot to reopen... Based on this: http://linuxfromscratch.org/pipermail/blfs-dev/2005-September/011477.html I would say that kconfig can't use qt4, only qt3. That would make this an upstream problem. That's probably true, but I was wondering if a conditional dependency (based on whether "qt" was set in a user's USE flags) for qt3 might not be a good idea. Otherwise, I end up using menuconfig, since gconfig seems to act sort of funny to me (I can't select options as I would like, something that I can do w/ menuconfig). Just wondering - it isn't like Qt can't be slotted, since it clearly was on my old system... (In reply to comment #5) > That's probably true, but I was wondering if a conditional dependency (based on > whether "qt" was set in a user's USE flags) for qt3 might not be a good idea. > Otherwise, I end up using menuconfig, since gconfig seems to act sort of funny > to me (I can't select options as I would like, something that I can do w/ > menuconfig). Just wondering - it isn't like Qt can't be slotted, since it > clearly was on my old system... Qt *is* slotted. If you don't want QT4, then package.mask it. USE="qt" is a bad use flag for this, should be USE="X" instead, but I really dislike an idea of such dependencies and use flags for kernels. Upstream bug, feel free to report it to them if you can provide advice where it is going wrong. No, we won't be adding any extra dependencies to kernels at this time. *** Bug 301608 has been marked as a duplicate of this bug. *** *** Bug 301608 has been marked as a duplicate of this bug. *** *** Bug 307491 has been marked as a duplicate of this bug. *** *** Bug 307491 has been marked as a duplicate of this bug. *** *** Bug 308001 has been marked as a duplicate of this bug. *** |