From owner-freebsd-ports@FreeBSD.ORG Sat Aug 27 13:08:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C537C1065670 for ; Sat, 27 Aug 2011 13:08:49 +0000 (UTC) (envelope-from ttsestt@gmail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9E08FC08 for ; Sat, 27 Aug 2011 13:08:49 +0000 (UTC) Received: by pzk33 with SMTP id 33so13479920pzk.18 for ; Sat, 27 Aug 2011 06:08:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:message-id:user-agent :mime-version:content-type; bh=zm5lQ7oaOG2dM/Q8ifMzfaFTLKgwgPIQO69y3md4FKA=; b=BCQK0g5OFQ6HlQcQHuKgkxD7WALsI9hdHw7HB5OkZrDvo6p9GKrGWKTVbJ+s8szpvO 4z0UD8pZlZd1EKF8WKI73USEdy13f7p6pfDkDnbIOaPxrSq8jY8mKr5XA5tgQZB0UgpQ JKO+sT0iT7qj+oxMfqL56NYgaOxyVfxxDkbZQ= Received: by 10.142.133.3 with SMTP id g3mr1156940wfd.82.1314450529148; Sat, 27 Aug 2011 06:08:49 -0700 (PDT) Received: from localhost (tor-exit-router42-readme.formlessnetworking.net. [199.48.147.42]) by mx.google.com with ESMTPS id r9sm6985691pbs.11.2011.08.27.06.08.46 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 06:08:48 -0700 (PDT) From: Test Rat To: Chris Rees References: <20110826172328.67f707d7@cox.net> <1314402348.13483.6.camel@xenon> <867h5zt6gd.fsf@gmail.com> Date: Sat, 27 Aug 2011 17:08:43 +0400 Message-ID: <867h5zm278.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-ports@freebsd.org Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2011 13:08:49 -0000 Chris Rees writes: >> >> Carmel writes: >> >> > So, after rebuild World/Kernel and installing same and then >> >> > rebuilding the nvidia-driver, all is well again. >> >> > >> >> > Now, in my not so humble opinion, there should be some sort of >> >> > warning in the driver dialog, or at least in the port description >> >> > that warns of this behavior. It could have save3d me several hours >> >> > of needless searching. Hours that I will never get back. :) [...] > Really, the proper fix would be to make kldload give a more descriptive > error, but IIRC this is much easier said than done... There are a few ports that use SRC_BASE and are *not* kernel modules, e.g. devel/linux_kdump devel/linuxthreads sysutils/lsof > I don't think doing more clever stuff in the port is the solution; It's not > specific to that port. What about bsd.port.mk bailing out early if kernel sources are for different version? It was in the patch you quoted but probably have not read.