>>> Emerging (5 of 8) net-misc/openconnect-7.06-r1::gentoo * openconnect-7.06.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * vpnc-scripts-20140806.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/4.1.6-gentoo/build * Found sources for kernel version: * 4.1.6-gentoo * Checking for TUN/TAP support ... * Please enable TUN/TAP support in your kernel config, found at: * * Device Drivers ---> * [*] Network device support ---> * <*> Universal TUN/TAP device driver support * * and recompile your kernel ... * ERROR: net-misc/openconnect-7.06-r1::gentoo failed (setup phase): * no CONFIG_TUN support detected! * * Call stack: * ebuild.sh, line 93: Called pkg_setup * openconnect-7.06-r1.ebuild, line 73: Called tun_tap_check * openconnect-7.06-r1.ebuild, line 58: Called die * The specific snippet of code: * die "no CONFIG_TUN support detected!"
Created attachment 410868 [details] openconnect-7.06-r1.ebuild Removed the die and modified the eerror to ewarn.
(In reply to Matthew Schultz from comment #1) Thanks, but I committed a larger change. We don't need to give the user a tutorial on navigating menuconfig. commit 10af1d23d759ef64f97126f5a588b2ca49bdef00 Author: Mike Gilbert <floppym@gentoo.org> Date: Wed Sep 2 10:40:50 2015 -0400 net-misc/openconnect: Make CONFIG_TUN check non-fatal Also move the check to pkg_pretend, and remove the custom error messaging. Package-Manager: portage-2.2.20
