Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 209027 - net-misc/hamachi-0.9.9.9_p20-r2 emerge failed on pkg_setup() (kernel config not found)
Summary: net-misc/hamachi-0.9.9.9_p20-r2 emerge failed on pkg_setup() (kernel config n...
Status: RESOLVED DUPLICATE of bug 87242
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 212805 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-02-05 19:45 UTC by Davide Cendron (RETIRED)
Modified: 2008-03-09 10:11 UTC (History)
1 user (show)

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


Attachments
hamachi-0.9.9.9_p20-r2.ebuild.patch (hamachi-0.9.9.9_p20-r2.ebuild.patch,578 bytes, patch)
2008-02-05 19:47 UTC, Davide Cendron (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Cendron (RETIRED) gentoo-dev 2008-02-05 19:45:50 UTC
net-misc/hamachi-0.9.9.9_p20-r2 fails to emerge with the following error:

>>> Emerging (1 of 1) net-misc/hamachi-0.9.9.9_p20-r2 to /
 * hamachi-0.9.9.9-20-lnx.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                                                                 [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                             [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                            [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                           [ ok ]
 * checking hamachi-0.9.9.9-20-lnx.tar.gz ;-) ...                                                                                                                                [ ok ]
 * Checking your kernel configuration for TUN/TAP support.
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.
 *
 * ERROR: net-misc/hamachi-0.9.9.9_p20-r2 failed.
 * Call stack:
 *                       ebuild.sh, line 1717:  Called dyn_setup
 *                       ebuild.sh, line  768:  Called qa_call 'pkg_setup'
 *                       ebuild.sh, line   44:  Called pkg_setup
 *   hamachi-0.9.9.9_p20-r2.ebuild, line   38:  Called check_extra_config
 *               linux-info.eclass, line  425:  Called require_configured_kernel
 *               linux-info.eclass, line  145:  Called die
 * The specific snippet of code:
 *              die "Kernel not configured; no .config found in ${KV_OUT_DIR}"
 *  The die message:
 *   Kernel not configured; no .config found in
 *

It seems to not set KV_OUT_DIR properly (see last row)

Reproducible: Always

Steps to Reproduce:
1. unmask net-misc/hamachi (if on stable)
2. emerge hamachi

Actual Results:  
emerge of net-misc/hamachi fails with an error.

Expected Results:  
net-misc/hamachi should emerge smoothly :)
Comment 1 Davide Cendron (RETIRED) gentoo-dev 2008-02-05 19:47:21 UTC
Created attachment 142745 [details, diff]
hamachi-0.9.9.9_p20-r2.ebuild.patch

Here's a working patch to fix the problem (and improve the ebuild output in case of errors, using the proper eclass vars)
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2008-02-05 21:21:08 UTC
(In reply to comment #0)

Dunno how's this fixing the real problem? This is just hiding that linux-info eclass fails to work properly with KBUILD_OUTPUT.


*** This bug has been marked as a duplicate of bug 87242 ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2008-03-09 10:11:49 UTC
*** Bug 212805 has been marked as a duplicate of this bug. ***