From nobody Thu Feb 15 20:37:37 2024 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TbRhV4vVJz5B8Zv for ; Thu, 15 Feb 2024 20:37:46 +0000 (UTC) (envelope-from jo@durchholz.org) Received: from www382.your-server.de (www382.your-server.de [78.46.146.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TbRhT5P0cz4HQQ for ; Thu, 15 Feb 2024 20:37:45 +0000 (UTC) (envelope-from jo@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=fdThKkxx; spf=pass (mx1.freebsd.org: domain of jo@durchholz.org designates 78.46.146.228 as permitted sender) smtp.mailfrom=jo@durchholz.org; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=durchholz.org; s=default2202; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=6Pv5Uw32lT6EJLu8V5U9pE+C6gs4OGItLR2bMy1L238=; b=fdThKkxxneuFRpPBUMLSjbhlac O+G3j9+1F+MJudOpbxQIIfKBS8DVe+KtmBLaQLpGETfzXxLACkFdCWfJzpH0m3R0NDvFoI0h/+86T Bkq6TcZnN0ic4iU2QwdPJPovYnlgqjQzV8k6g6O48RqP8ECc7r45NNWyhZW9uJofQK10eaM8njrwq 20dd19lGaSI/ZRibEyRz/Ngf6QgROZ8hXTz7zfaF5z+xtti+iXtN9uXCuZiCQvbiJCfLy2SpPKehT odzzXLrJ1wfXFcNZItsgrtqtDt0+7fBvJu6pxVqu8j7X6gHiYlmlAa7Gb/GQ34wEXdvNglNNk4gFg zKg+QaCg==; Received: from sslproxy03.your-server.de ([88.198.220.132]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1raiUE-000Mmz-0k for virtualization@freebsd.org; Thu, 15 Feb 2024 21:37:38 +0100 Received: from [81.221.201.210] (helo=[192.168.178.48]) by sslproxy03.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1raiUD-000ShO-T8 for virtualization@freebsd.org; Thu, 15 Feb 2024 21:37:37 +0100 Message-ID: Date: Thu, 15 Feb 2024 21:37:37 +0100 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Won't contribute KVM build :-( (was: Contributing the build of a KVM image) Content-Language: en-US To: virtualization@freebsd.org References: From: Jo Durchholz In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: jo@durchholz.org X-Virus-Scanned: Clear (ClamAV 0.103.10/27186/Thu Feb 15 10:23:30 2024) X-Rspamd-Queue-Id: 4TbRhT5P0cz4HQQ X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; R_SPF_ALLOW(-0.20)[+a]; R_DKIM_ALLOW(-0.20)[durchholz.org:s=default2202]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[durchholz.org]; HAS_X_AS(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[virtualization@freebsd.org]; DKIM_TRACE(0.00)[durchholz.org:+] On 29.01.24 23:41, Jo Durchholz wrote: > Hi all, > > where do I turn to if I want to contribute to the FreeBSD build/release > process so that a KVM image will be built? > > This is not actually about virtualization per se but about the > build&release process, so I guess I'd be wrong here. I'm sorry to report that I can't do it, due to lack of feedback and incomplete/outdated documentation. Current roadblock is that I don't see a list of valid value for TARGET and TARGET_ARCH. After much searching, I found that "make targets" will give me that. Trying "make.py targets" -> complains about unset MAKEOBJDIRPREFIX. Some Internet searches later I know it's just a temporary build directory, so I put it in ~/obj, export MAKEOBJDIRPREFIX=~/obj -> complains: Could not infer value for $XCC. Either set $XCC or pass --cross-bindir=/cross/compiler/dir/bin "which clang" gives me /usr/bin/clang, so why does it not find clang? Now trying src/tools/build/make.py --cross-bindir=/usr/bin targets Could not infer value for $XCPP: /usr/bin/clang-cpp Ehm... sure, no, there is no such thing as a clang-cpp. I have a clang-cpp-14. Not sure why there's no clang-cpp, https://clang.llvm.org/docs/UsersManual.html says it should be there, but then again the Debian package maintainer may have run into naming conflicts and decided to give a version-specific name. I could obviously use XCPP=/usr/bin/clang-cpp, but given that I haven't gotten an answer to my previous question and that I have to expect more roadbumps ahead, plus I'll have to learn the freebsd Arcanist tooling just to submit a patch... well, it's been death by a thousand papercuts, and sorry, that's more work than I'm willing to invest, and it's a KO anyway since I'm making something highly security-critical and I'm not confident I can learn enough of FreeBSD to make no stupid mistakes. So... Linux it will be. It's sad, because FreeBSD has a pretty impressive security track record that I'd really like to leverage, but if I can't achieve the traction to bring that advantage to the road, it's not useful for me - I'd need a competent FreeBSD person for that, and I don't have one, and my own competence seems insufficient. Please not that THIS IS NOT A CRITICISM OF FREEBSD. It's just a single data point, for anybody who wants to know what kinds of things hold back FreeBSD adoption; if there's no need for that (possibly because other things have higher priority, or a gazillion of other possible reason), please pretend I never wrote this. And, thanks for making FreeBSD. I know it's a lot of work. Regards, Jo