From owner-freebsd-ports@freebsd.org Wed Dec 27 03:48:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C7D6E9F8D2 for ; Wed, 27 Dec 2017 03:48:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::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 29D9B75921 for ; Wed, 27 Dec 2017 03:48:17 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x235.google.com with SMTP id q22so13714400uaa.9 for ; Tue, 26 Dec 2017 19:48:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=K8FOXlKlOaKOQgnGfHPqRXlC6bhRzhSULK1mxPBFY6U=; b=RRu/O2g2YIQ/fUohcBZSsRYdhURR2bGdL7Vu8Zvkq8L/g+FfgSqSDDmNN1VhcNaAGx ZXK6EN31ERVqfrI57uP9cqsm+Z0zGz4gnukvD1N0VXfms+x0toPdKZpzA/yKtAaxuDPi smP3wbolXpeq7FMTHyUcn1oAJiMsnz4KyKlNMwAFpce/P24so+Ej9WhuhYal/tRQnSWv qYw49+rwxjZxJMs/ok+v4fxzNTn8G6PFEBcExbnwRv+1kfFuJ4G+v0Ut/ZLytAbdvHRT Qf4+KeQjZ3YUQR9cTfXeV1SrZUZLIXjHZHt2B5IamA9tLKQDznNsElr4mepJ6Tds7anD N6jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=K8FOXlKlOaKOQgnGfHPqRXlC6bhRzhSULK1mxPBFY6U=; b=BWtQtNC5fPXXKEZVfVVXZg52dB6P0UAy5Y+GgAY50yEOg163L81KtQppKYGEtYl8CW 1yp4nyv2B865o7pn/SZP6AHP6zGkUvbxhrfUgXY3aaNb3g0rCdHk+9XzFpACA7x3I2+Q JEooqLGGa534F7MxX4d+uzdJPv0T7SMgK5KubD+cfq1IONc++rNFZym6KlXqBopDRKeD oGIBxvJ+wkPxtrQ3+tDuGgkViDzS4TM8eSTaJQpAlxamkv5xSFDjp51GoESouiSbuiVI akH5wt1l59HaucoSZGbwqrU/P/hNrqNSssucljJ5f4j35jD4bJNV6t1HKTxzWy+M876+ X7dA== X-Gm-Message-State: AKGB3mJgZrIEIUVRgDVwP8eMmp2eLPDvi5FLy44NDbVemNCr5LE/AOLl Kk/fyhcKv5Wq3a+VRQDSgW1pYITeQy06EPMvdYUwKAm5 X-Google-Smtp-Source: ACJfBotCEfbIhVsRYnHRv0herFBJKsoF7+DppXpM5g88Qed6E9MEg+2eEeMCp06ximGeNZD3Yz+IuAkK5QWBpuSATOA= X-Received: by 10.159.61.8 with SMTP id l8mr12151190uai.41.1514346495980; Tue, 26 Dec 2017 19:48:15 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Tue, 26 Dec 2017 19:48:15 -0800 (PST) In-Reply-To: References: <4DB6D455-3F50-4AC9-83A4-0AFD06B6058C@FreeBSD.org> From: Kevin Oberman Date: Tue, 26 Dec 2017 19:48:15 -0800 X-Google-Sender-Auth: ptSy7A48o_7T7T3EW36pJfGGG3M Message-ID: Subject: Re: Of LSOF To: Dave Horsfall Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2017 03:48:17 -0000 On Tue, Dec 26, 2017 at 4:20 PM, Dave Horsfall wrote: > On Wed, 27 Dec 2017, Dimitry Andric wrote: > > Binary packages are built on the oldest supported 10.x release, which >> currently is 10.3. I think that lsof is just one of the few programs that >> care about this, and show a warning. This is probably because lsof pokes >> around in half-documented (or undocumented) system structures, which might >> change even in minor releases. >> > > Thanks for that. > > The path of lowest resistance is to ignore the warning, otherwise build >> (or package) the port yourself. >> > > Which I discovered last year required that kernel sources be installed > (which I didn't have at the time; I didn't build this system) because it > wanted a certain #include file. I reported this in a PR saying that > perhaps all header files be shipped, but I dunno what happened. > > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will > suffer." > lsof pokes it's fingers into the kernel a LOT and the official recommendation (from the author) is to always rebuild it when the kernel is rebuilt. I have had lsof fail in the past on STABLE systems when internal changes are made to the kernel that do not affect the documented APIs, so there is really a reason for this. It does require that kernel sources be present as they may have changed between versions and that would cause lsof to fail. Putting header files into the port is a non-starter as they MUST match the kernel on which lsof is built. I added lsof to PORTS_MODULES so it is rebuilt with any new kernel on my stable system and on one release system so I can use that package to install elsewhere rather then use the repo package. Now that 10.3 is EOL I would expect that the package built for 10-STABLE would be built on 10.4-RELEASE, but I don't know for sure. It should be and the next quarterly should be 10.4 based, too. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683