From owner-freebsd-current@freebsd.org Thu Feb 18 13:25:41 2021 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 6D6AA537DC7 for ; Thu, 18 Feb 2021 13:25:41 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DhFnw352Lz4Vx8; Thu, 18 Feb 2021 13:25:40 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 4DhFns02tqz3nnN; Thu, 18 Feb 2021 13:25:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1613654736; bh=r1ClWarRVORkJN8a5rH8YTFY ahlWJAYX4Spd4GZrqB0=; b=wmQ8Ii//CdO5OYA+bfcpVMNb9rLMhrHd4uR2iy7G oNeFp9uGSd+D4ask35IsrVqImIvR8ZZBJa8Xf1A8KK+IlnwJ+z7xvzauO8ED4e16 ovKliJroGVV0V26ly507YAYsyEDAxZ7rJ/ZH3IQz1mmkqkJsv6AW2J6IwPLJL2pV gaA= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id usifJOCinTjv; Thu, 18 Feb 2021 13:25:36 +0000 (UTC) Received: from garnet.daemonic.se (unknown [IPv6:2001:470:dca9:1201:d810:2543:e8a2:7c1b]) by mail.daemonic.se (Postfix) with ESMTPSA id 4DhFnr1rVQz3nJp; Thu, 18 Feb 2021 13:25:36 +0000 (UTC) Subject: Re: buildkernel: don't know how to make cleandir in drm-current-kmod To: Ruslan Makhmatkhanov , FreeBSD Current References: <22f360b7-3b6d-61c6-e05e-579b8699b9ee@daemonic.se> <81540cb5-81af-3a45-e9ca-c00b20a6ae6e@FreeBSD.org> From: Niclas Zeising Message-ID: <94a72c91-6a05-9123-7538-cdfbe6714e14@daemonic.se> Date: Thu, 18 Feb 2021 14:25:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <81540cb5-81af-3a45-e9ca-c00b20a6ae6e@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4DhFnw352Lz4Vx8 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=daemonic.se header.s=20151023 header.b=wmQ8Ii//; dmarc=pass (policy=none) header.from=daemonic.se; spf=pass (mx1.freebsd.org: domain of zeising@daemonic.se designates 2607:f740:d:20::25 as permitted sender) smtp.mailfrom=zeising@daemonic.se X-Spamd-Result: default: False [-3.81 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f740:d:20::25:from]; R_DKIM_ALLOW(-0.20)[daemonic.se:s=20151023]; FREEFALL_USER(0.00)[zeising]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; R_SPF_ALLOW(-0.20)[+mx]; ARC_NA(0.00)[]; SPAMHAUS_ZRD(0.00)[2607:f740:d:20::25:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[daemonic.se:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[daemonic.se,none]; NEURAL_HAM_SHORT(-0.81)[-0.807]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; TAGGED_FROM(0.00)[freebsd]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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: Thu, 18 Feb 2021 13:25:41 -0000 On 2021-02-18 09:41, Ruslan Makhmatkhanov wrote: > Niclas Zeising wrote on 2/18/21 9:55 AM: >> On 2021-02-18 06:32, Ruslan Makhmatkhanov wrote: >>> Hello, >>> >>> trying to build kernel from >>> commit f61e92ca5a23450bc28169bbdd71d7674df98c19 (HEAD -> main,=20 >>> origin/main, origin/HEAD) >>> Author: Glen Barber >>> Date:=C2=A0=C2=A0 Wed Feb 17 23:00:03 2021 -0500 >>> >>> world built ok, but then I have this on make kernel: >>> >>> =3D=3D=3D> zlib (cleandir) >>> rm -f export_syms machine x86 zlib.ko zlib.kld zcalloc.o zlib_mod.o=20 >>> adler32.o compress.o crc32.o deflate.o inffast.o inflate.o inftrees.o= =20 >>> trees.o uncompr.o zutil.o offset.inc genoffset.o >>> rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS >>> =3D=3D=3D> drm-current-kmod (cleandir) >>> make[3]: don't know how to make cleandir. Stop >>> >>> make[3]: stopped in /usr/local/sys/modules/drm-current-kmod >>> *** Error code 2 >>> >>> Stop. >>> make[2]: stopped in /usr/obj/mnt/hdd/src/amd64.amd64/sys/Z1 >>> *** Error code 1 >>> >>> Stop. >>> make[1]: stopped in /mnt/hdd/src >>> *** Error code 1 >>> >>> Stop. >>> make: stopped in /mnt/hdd/src >>> >>> Tried to reinstall drm-current-kmod to not avail. >>> >> >> Can you check that you have the folder=20 >> /usr/local/sys/modules/drm-current-kmod, and that there are sources=20 >> inside? >> drm-current-kmod no longer installs sources by default, please check=20 >> if you have enabled that option locally. >> Regards >=20 >=20 >=20 > That's what was installed by the package from official repo. Now I buil= t=20 > it locally with making sure SOURCE option is enabled and kernel now=20 > builds. Thanks. >=20 > So, was it some temporary decision to exclude sources from the package=20 > by default, or since now I should manually build drm-kmod package at=20 > every update? >=20 We disabled the source option because it caused too much issues. It catches people by surprise sometimes when the drm-kmod modules are=20 rebuilt automatically with the kernel, even when they are not in /usr/src= . The biggest problem though is that the general workflow often is to=20 rebuild the world, then the kernel, then update ports. This means that=20 the drm-kmod srources won't be updated before the kernel is built,=20 causing build failures (if you need an updated drm-kmod because of=20 changes in the kernel). Generally, the recommended way is to first buildworld/buildkernel,=20 install the new kernel, remove the old drm-current-kmod before booting=20 the new kernel, and then rebuild drm-current-kmod from ports with the=20 new kernel. Regards --=20 Niclas