656 – Environment variable not set when calling emerge with "--buildpkg"

Bug 656 - Environment variable not set when calling emerge with "--buildpkg"

Summary: Environment variable not set when calling emerge with "--buildpkg"

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-02-11 12:29 UTC by Holger Benl
Modified:	2011-10-30 22:20 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Holger Benl 2002-02-11 12:29:39 UTC

When I do "emerge --buildpkg alsa-driver", it fails. Reason: the environment
variable $KV isn't set and so emerge tries "./configure
--with-kernel=/usr/src/linux- --with-.....", which fails. When I do "emerge
alsa-driver", everything works fine.

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-02-11 13:23:32 UTC

Bevin, what do you think about adding a standard KV variable to portage that's
always defined as the version of the /usr/src/linux symlink, or "" if no such
link exists?  That would come in handy.

Comment 2 Daniel Robbins (RETIRED) gentoo-dev

2002-02-20 00:23:55 UTC

should be fixed on cvs now.  Fixed existing file without bumping rev.  Thanks
for the bug report.