Date: Sat, 10 May 2014 16:04:51 -0400 From: Thomas Hoffmann <trh411@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: delete-old issue with src.opts.mk Message-ID: <CAB7-odmvm7xOZGHr4KW3d6ogCaobnsG2p9s7Kfz1zS-CKTFKnA@mail.gmail.com> In-Reply-To: <A4BF7735-E337-40AB-9ADF-8852D8C2E436@gmail.com> References: <CAB7-od=9kEWBe6ZVtvQx9WnQYRACe1t76i7YAy479ghYmDKC_Q@mail.gmail.com> <A4BF7735-E337-40AB-9ADF-8852D8C2E436@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 10, 2014 at 3:54 PM, Warner Losh <imp@bsdimp.com> wrote: > > On May 10, 2014, at 9:45 AM, Thomas Hoffmann <trh411@gmail.com> wrote: > > > The other night I built a new -CURRENT at r265728. At delete-old it ask= ed > > 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 <http://src.opt.mk>" error. > > I=E2=80=99ve 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=E2=80=99t be now that I=E2= =80=99ve 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=E2=80=99t required to build ports. Well, it was for a couple of da= ys due to > a bug, but I=E2=80=99ve 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 =E2=80=98yes=E2=80=99) and then try virtu= albox-ose build > again. It should just work. If it doesn=E2=80=99t then send in a bug repo= rt 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=E2=80=99m= coming to > discover, and used in several non-obvious use cases that seem obvious aft= er > the bug report comes in=E2=80=A6 Sorry these slipped through the cracks i= n my > testing... > > Warner Thanks for the response. I'll follow your advice above when I build -CURRENT again tonight. No apology necessary. I build a new -CURRENT nearly every night and expect to run into a glitch every now and again. -Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB7-odmvm7xOZGHr4KW3d6ogCaobnsG2p9s7Kfz1zS-CKTFKnA>