From owner-freebsd-current@FreeBSD.ORG Sat May 10 20:01:46 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA6DF4F0 for ; Sat, 10 May 2014 20:01:46 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ABB76382 for ; Sat, 10 May 2014 20:01:46 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id kq14so5707444pab.24 for ; Sat, 10 May 2014 13:01:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=K5oWiIBi3CYTiFiuT1FPxe/4BFccd0rOpSKioX1f7lk=; b=AeCpDLpphjKpVIv/IwVZuUTfXL6NV7b4OWa/BJANylO+JeAyzWdJzNTb1+poFPJfPO eHjfrln/eKNtSG11ZLZNzXMuE2c1mJ+VsIyOhsDxIL7wwo+tgiPrJ1C07PJnFqHfHJ/e HbOAFjIBxH/nuIUtFKt51xY6TGou8+6jyZKSj+Xgj8fac/AXRg6oaDxskzrbS8rJk7T5 XHvJRJ6zQRxhQ+HZihP6iKttktpoTI/g4C44nXZgG2yknAlmdw0Jfc6e0/RPD2animMj M54rcxERTwhjfDRJ9h1P3vSpcJN4OHEN4/RSgo+D+TvyoXWycTxrSIPwd2CBVEsKdK6q gArg== X-Gm-Message-State: ALoCoQkPaYNxjJzi+pP/6IWp6rejvWvDhahWj7e4DAdjyMegcQCL+oEo137GPtqNXC1hO3jhyQWM X-Received: by 10.66.148.197 with SMTP id tu5mr36183644pab.108.1399751670345; Sat, 10 May 2014 12:54:30 -0700 (PDT) Received: from lgwl-achen.corp.netflix.com (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id gz11sm14293232pbd.1.2014.05.10.12.54.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 10 May 2014 12:54:29 -0700 (PDT) Sender: Warner Losh X-Google-Original-From: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: delete-old issue with src.opts.mk From: Warner Losh In-Reply-To: Date: Sat, 10 May 2014 13:54:28 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Thomas Hoffmann X-Mailer: Apple Mail (2.1874) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2014 20:01:47 -0000 On May 10, 2014, at 9:45 AM, Thomas Hoffmann wrote: > The other night I built a new -CURRENT at r265728. At delete-old it = asked > me if I wanted to "remove /usr/share/mk/src.opts.mk?" I said yes. > Subsequently an upgrade attempt for virtualbox-ose-4.3.10_1 failed = with a > "missing src.opts.mk " error. I=92ve fixed that. > Last night I built a new -CURRENT at 265793. At delete-old it asked me = if I > wanted to "remove /usr/share/mk/src.opts.mk?"again. I said no. = Subsequently > an upgrade for virtualbox-ose-4.3.10_1 succeded. You should say yes. > Three questions: > 1. Why is delete-old repeatedly asking me if I want to remove = /usr/share/mk/ > src.opts.mk? It seems to keep getting installed. It shouldn=92t be now that I=92ve = got things ironed out. > 2. Why is delete-old asking me if I want to remove something that is > required to build ports, well at least one port? I did not try to = build any > other ports, so maybe it was just a virtualbox-ose issue? It isn=92t required to build ports. Well, it was for a couple of days = due to a bug, but I=92ve fixed that bug. > 3. Should I keep src.opts.mk at delete-old or remove it? Remove it. It should ask you at most one more time. > I saw some discussion about src.opts.mk, but it centered around the = use of > WITHOUT_NIS, which is not my issue. Yea. I understand. The WITHOUT_NIS was a different, and subtle, bug that = I fixed as well. My advise: update to the tip of head, buildworld, install world, = delete-old (making sure you say =91yes=92) and then try virtualbox-ose = build again. It should just work. If it doesn=92t then send in a bug = report since I missed something when I fixed nvidia and cuse builds. Thanks for the report. I hope I can get this all ironed out for you. I = think I have already, but the build system is rather fragile, I=92m = coming to discover, and used in several non-obvious use cases that seem = obvious after the bug report comes in=85 Sorry these slipped through the = cracks in my testing... Warner=