From owner-freebsd-current@freebsd.org Wed Aug 14 20:49:55 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B0963BAA66; Wed, 14 Aug 2019 20:49:55 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4681tB1jjYz3wrS; Wed, 14 Aug 2019 20:49:53 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id y0DMhtVKoIhW9y0DOhq0IF; Wed, 14 Aug 2019 14:49:51 -0600 X-Authority-Analysis: v=2.3 cv=FcFJO626 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=FmdZ9Uzk2mMA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=ukcIUTkTVbqB7o9lrnYA:9 a=nP8rgmpX93VALr-r:21 a=DA6hQ6Newwfzqsrh:21 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from 5CG5030TVK-N.esitwifi.local (S0106788a207e2972.gv.shawcable.net [70.66.154.233]) by spqr.komquats.com (Postfix) with ESMTPSA id D19ABB9B; Wed, 14 Aug 2019 13:49:47 -0700 (PDT) Date: Wed, 14 Aug 2019 13:49:28 -0700 In-Reply-To: References: <67ca217f-b7de-8707-c4de-51e3f895d06f@FreeBSD.org> <469b61c7c939b4e70f4304eaeb73eaae9b1d4c9a.camel@freebsd.org> <20190814192353.166bd3e7d1af44a55a61c915@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: HEADSUP: drm-current-kmod now installs sources To: freebsd-current@freebsd.org, Ian Lepore , Niclas Zeising , Emmanuel Vadot , John Baldwin CC: x11@FreeBSD.org,current@FreeBSD.org From: Cy Schubert Message-ID: X-CMAE-Envelope: MS4wfNjJ29sFSkY3pMn199DyQvSe3+UG1IS5BPt3uUzZde+OcIhIPtYpnF4XvkxrxoCa+9x85fM4ZzE6W2KFhBIvX6et5P4zNSkvV1nN6Ac3aTDUXo6MPGCC OIA5XYbj4XBBfrmECHGj/0H11rDpKiZgIyVpf2Vkp+/FO3EKEyCJA+ldw5+2dsqlSwav2fO1JEB6PnO+WLhaEXKiIGh0xp9QvsqMcYtS414PoSYul30MDJoM yw3uFkUosK/m+mY+hsxSQr8re2dlP2lxjo+YVIRK0VmSyjaUpbkD/EkJg7KE84RqE+OLm5k02KayjAmjAxKweTG6Oe41Ev7UaeQqLJIr4/TxDAv1tuUmDT3Q HvyW0r7Q X-Rspamd-Queue-Id: 4681tB1jjYz3wrS X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of cy.schubert@cschubert.com has no SPF policy when checking 64.59.136.137) smtp.mailfrom=cy.schubert@cschubert.com X-Spamd-Result: default: False [-5.39 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.94)[-0.940,0]; RCVD_IN_DNSWL_NONE(0.00)[137.136.59.64.list.dnswl.org : 127.0.5.0]; RCPT_COUNT_SEVEN(0.00)[7]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.35)[ip: (-6.03), ipnet: 64.59.128.0/20(-3.17), asn: 6327(-2.46), country: CA(-0.09)]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11, 233.154.66.70.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Wed, 14 Aug 2019 20:49:55 -0000 On August 14, 2019 11:04:20 AM PDT, Ian Lepore wrote: >On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote: >> On 2019-08-14 19:23, Emmanuel Vadot wrote: >> > On Wed, 14 Aug 2019 10:13:48 -0700 >> > John Baldwin wrote: >> >=20 >> > > On 8/14/19 9:22 AM, Ian Lepore wrote: >> > > > This all sounds vaguely wrong, backwards, to me=2E A developer >> > > > who is >> > > > using a given module on their build system might want that >> > > > module to be >> > > > rebuilt automatically, but only if the build parameters match >> > > > those of >> > > > the running build host system=2E >> > > >=20 >> > > > If my build host is running freebsd 12 amd64 and I'm doing a >> > > > build for >> > > > freebsd 13 armv7, I have no interest in automatic rebuilds of >> > > > an amd64 >> > > > driver module for a different OS arch and version just because >> > > > that >> > > > module happens to be installed on the system I use to do >> > > > crossbuilds=2E >> > > >=20 >> > > > My objections are theoretical=2E=2E=2E this automation just seems >> > > > improperly >> > > > designed to me=2E But it won't actually affect me in any way, >> > > > because I >> > > > don't build video driver modules from ports, and I don't run >> > > > freebsd >> > > > current on my build host machine=2E Probably the number of >> > > > people doing >> > > > crossbuilding is small enough that nobody else is going to >> > > > object to >> > > > this "the whole world is amd64" automation=2E >> > >=20 >> > > You assume DRM is amd64-only when it is definitely not=2E It also >> > > has >> > > suitable guards in its Makefile to only build the relevant kernel >> > > modules on supported architectures=2E >> >=20 >> > I clearly don't want to spend time to build the drm and radeon >> > modules >> > when I'm hacking on arm64=2E >> > Shouldn't LOCAL_MODULE have ${TARGET}=2E${TARGET_ARCH} as a >> > subdirectory ? So when you install drm-kmod-* it will only install >> > the >> > source in /usr/local/modules/${TARGET}=2E${TARGET_ARCH}/ ? (or >> > whatever >> > the correct dir is)=2E >> >=20 >>=20 >> I'm not sure what you're trying to accomplish=2E I might be=20 >> misunderstanding completely, but, at least the drm ports have >> safeguards=20 >> in their makefiles so they'll only be built for those arches where >> there=20 >> is support, and only the modules needed, as an example, i915kms=2Eko >> will=20 >> only be built on amd64 and i386, if that's what you're worried about=2E >> Regards > >I can't understand what you guys are not-understanding=2E New machinery >has been added that says "if some module source code exists in this >absolute fixed location on the build machine, then whenever you do any >kernel build for any OS version or any arch, rebuild that module source >code so that the the build machine's video drivers stay in sync with >the build machine's kernel=2E" > >Do you not see that for some of us, only a tiny fraction of the builds >done (maybe none of them at all) involve the kernel for the build host >machine or the video drivers for the build host machine? And yet, for >us, every build we do will now inapppropriately rebuild this video >driver module which has nothing to do with the machine the build is >targeting=2E > >And it's not just about crossbuilds, because it's about versions too=2E= =20 >Even when a developer is running 13-current and wants their video >driver rebuilt and installed automatically along with the kernel, >they're certainly going to want that to happen only when they're >building 13-current=2E If they're doing a test-build for 12-stable they >certainly aren't going to want to build and install that video driver=2E > >-- Ian > >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" How about build/install when arch is the same as local machine arch? --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E