Hi everyone,
This issue has come up in a few bugs so I want to bounce it off the
community. When building packages that need a configured kernel source
tree, many ebuilds inherit linux-info to find configuration info about
the kernel. However, there is the running kernel with its
On Thu, Feb 21, 2013 at 1:42 PM, Anthony G. Basile
bas...@opensource.dyc.edu wrote:
Hi everyone,
This issue has come up in a few bugs so I want to bounce it off the
community. When building packages that need a configured kernel source
tree, many ebuilds inherit linux-info to find
On 21 February 2013 18:49, Mike Gilbert flop...@gentoo.org wrote:
On Thu, Feb 21, 2013 at 1:42 PM, Anthony G. Basile
bas...@opensource.dyc.edu wrote:
Hi everyone,
This issue has come up in a few bugs so I want to bounce it off the
community. When building packages that need a configured
On Thu, Feb 21, 2013 at 12:42 PM, Anthony G. Basile
bas...@opensource.dyc.edu wrote:
Hi everyone,
This issue has come up in a few bugs so I want to bounce it off the
community. When building packages that need a configured kernel source
tree, many ebuilds inherit linux-info to find
On 02/21/2013 06:12 PM, Doug Goldstein wrote:
On Thu, Feb 21, 2013 at 12:42 PM, Anthony G. Basile
bas...@opensource.dyc.edu wrote:
Hi everyone,
This issue has come up in a few bugs so I want to bounce it off the
community. When building packages that need a configured kernel source
tree, many
On Thu, Feb 21, 2013 at 8:42 PM, Anthony G. Basile
bas...@opensource.dyc.edu wrote:
there is the kernel source tree
(/usr/src/linux if it exists and is configured)
The kernel can also be split (KV_DIR + KV_OUT_DIR), with relevant
headers located in both directories. E.g., [1].
[1]
