Date: Wed, 21 Feb 2018 20:43:41 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: pkg does not recognize correct kernel version Message-ID: <alpine.BSF.2.21.1802212040030.24158@mail.fig.ol.no> In-Reply-To: <op.zesu3yhqkndu52@klop.ws> References: <op.zeo60hflkndu52@klop.ws> <eeae41de-d83b-93b4-0b69-bb62c9e84bb4@gwdg.de> <op.zeo9mlutkndu52@klop.ws> <80b54e13-7e6c-a52e-4d42-16903e16e67b@gwdg.de> <20180219210551.GE94212@kib.kiev.ua> <op.zepfusvakndu52@klop.ws> <alpine.BSF.2.21.1802201128270.24158@mail.fig.ol.no> <op.zesu3yhqkndu52@klop.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Feb 2018 20:01+0100, Ronald Klop wrote: > On Tue, 20 Feb 2018 11:30:52 +0100, Trond Endrestøl > <Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > On Mon, 19 Feb 2018 23:38+0100, Ronald Klop wrote: > > > > > Does this mean I always have to do a *clean* buildworld after every > > > version > > > bump? This takes ages. > > > > Yes, I've come to the conclusion that whenever __FreeBSD_version in > > sys/sys/param.h is incremented, then it's time to blow away /usr/obj, > > recreate everything to ensure the correct value of osversion in the > > .note.tag section of each executable, and reinstall base prior to > > updating localbase. See PR 225104 for more details, > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225104. > > > > pkg: Newer FreeBSD version for package gnome-menus: > - package: 1200058 > - running kernel: 1200056 > > So it says "running kernel", but it actually checked "version of > FreeBSD_version while building /bin/sh" or something like that. > This sounds over-engineered and (more important) confusing. I tried the simply approach of running "make clean; make build" in /usr/src/bin/sh, hoping it would generate binaries with the correct osversion in the .note.tag section. Boy, I couldn't be more wrong. Hence my (possibly wrongful) conclusion of wiping /usr/obj whenever osversion is increased. I'm probably missing a simpler step. -- Trond. From owner-freebsd-current@freebsd.org Wed Feb 21 19:49:40 2018 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 792D1F245C0 for <freebsd-current@mailman.ysv.freebsd.org>; Wed, 21 Feb 2018 19:49:40 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BBC0F6EC72 for <freebsd-current@freebsd.org>; Wed, 21 Feb 2018 19:49:39 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id g72so4053697lfg.5 for <freebsd-current@freebsd.org>; Wed, 21 Feb 2018 11:49:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mBgr/pfxTHypDvj1jgA8MLbxGa5sNLWtEEJYuQszE1M=; b=r+T3GYciULouFp6Bhn/8PA5KH1Eoj9+ckMgGMOJEOK/Q4iRZZY2OKUOIvXiMxx5hXa 2kpNIVQaYtwOUlxXECDieVqJNfxht3h6V0ir55AEayGlcDN80PNA8Gon5IrDNKS1iaUX qW5JKHZcRShlFsNODLs4zq8cPYE+kkBlR2cOwRr/2ZvQspEO5fdjiMuxnY6U+DFrDKYc 1ap0hq6x/jZSKPREzmMhYwiEsVlB7O5iBKCc2KseZ5nCyYGrS3ZHEeLuG96uHQbl8kki Nq3GzZf2q8zjuFzwfIWJHQ/5/zEAByvxfXTe6xQQOev0ebMEQJ647Xn54StoQKHrHyJg FCcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mBgr/pfxTHypDvj1jgA8MLbxGa5sNLWtEEJYuQszE1M=; b=My6k47h21y1Z8qYrQoFvuiljDQBRsnHOfqm941nCf168z4HtpIpR6mMGJW3fu9Z1BB isBWI4/ItfYim+gflgAY9PxO6O8/UaRheGAnOg3onoeRP554DcwQWwaSRJRnzMjULQRq ZJGvKvBxLWetMQvfnCJKZxzxYrkUH8EjxBfTPdrG0KZr4/hzMp3ocoZYbvhJzrmI0a4f KTnMoZ3fEvYK80V5mROwW/PPlfl2ypuVD7muzuYya+d8MJe2Z1i3zJ359yyyIV+o3KnN UUx73X1PJWuDDQZLAXqnQTIL46yqJui0H/kgXv1XTNX6xRIJHwjz2pkFtIjbBnBiJUGg xVWQ== X-Gm-Message-State: APf1xPCmEFaOBuZpfZ0Al3vAtu0jsdG1ennPRtrlQo/UX/8q7WUsYQsT lUnA9+JlJ7lBvrOsuhTIKOBPeeH2d3pWYcPl1Kw= X-Google-Smtp-Source: AH8x224UrnFb4A1YfSP812X6jgMgtOoXq7aI8nF6FF97LtKTH3DWJglvEAfYYQMh/a1/NhGY6UK24xOc63gKfm3XH48= X-Received: by 10.25.34.81 with SMTP id i78mr3193474lfi.50.1519242578024; Wed, 21 Feb 2018 11:49:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.3.10 with HTTP; Wed, 21 Feb 2018 11:49:37 -0800 (PST) Received: by 10.46.3.10 with HTTP; Wed, 21 Feb 2018 11:49:37 -0800 (PST) In-Reply-To: <alpine.BSF.2.21.1802212040030.24158@mail.fig.ol.no> References: <op.zeo60hflkndu52@klop.ws> <eeae41de-d83b-93b4-0b69-bb62c9e84bb4@gwdg.de> <op.zeo9mlutkndu52@klop.ws> <80b54e13-7e6c-a52e-4d42-16903e16e67b@gwdg.de> <20180219210551.GE94212@kib.kiev.ua> <op.zepfusvakndu52@klop.ws> <alpine.BSF.2.21.1802201128270.24158@mail.fig.ol.no> <op.zesu3yhqkndu52@klop.ws> <alpine.BSF.2.21.1802212040030.24158@mail.fig.ol.no> From: Andreas Nilsson <andrnils@gmail.com> Date: Wed, 21 Feb 2018 20:49:37 +0100 Message-ID: <CAPS9+St7kFAgjJSFsrrq9Lu9Gb48bdis6bjkxR-GeYKVhZCPgw@mail.gmail.com> Subject: Re: pkg does not recognize correct kernel version To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= <Trond.Endrestol@fagskolen.gjovik.no> Cc: Current FreeBSD <freebsd-current@freebsd.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 21 Feb 2018 19:49:40 -0000 As of pkg-1.10.5 it will ask if you wish to proceed which makes this much easier to deal with. Best regards Andreas On Feb 21, 2018 20:45, "Trond Endrest=C3=B8l" < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Wed, 21 Feb 2018 20:01+0100, Ronald Klop wrote: > > > On Tue, 20 Feb 2018 11:30:52 +0100, Trond Endrest=C3=B8l > > <Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > > > On Mon, 19 Feb 2018 23:38+0100, Ronald Klop wrote: > > > > > > > Does this mean I always have to do a *clean* buildworld after every > > > > version > > > > bump? This takes ages. > > > > > > Yes, I've come to the conclusion that whenever __FreeBSD_version in > > > sys/sys/param.h is incremented, then it's time to blow away /usr/obj, > > > recreate everything to ensure the correct value of osversion in the > > > .note.tag section of each executable, and reinstall base prior to > > > updating localbase. See PR 225104 for more details, > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225104. > > > > > > > pkg: Newer FreeBSD version for package gnome-menus: > > - package: 1200058 > > - running kernel: 1200056 > > > > So it says "running kernel", but it actually checked "version of > > FreeBSD_version while building /bin/sh" or something like that. > > This sounds over-engineered and (more important) confusing. > > I tried the simply approach of running "make clean; make build" in > /usr/src/bin/sh, hoping it would generate binaries with the correct > osversion in the .note.tag section. Boy, I couldn't be more wrong. > Hence my (possibly wrongful) conclusion of wiping /usr/obj whenever > osversion is increased. I'm probably missing a simpler step. > > -- > Trond. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1802212040030.24158>