From nobody Sat Feb 10 23:58:55 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 4TXSP61lY8z58ttX for ; Sat, 10 Feb 2024 23:59:06 +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 4TXSP51jDYz4rrF for ; Sat, 10 Feb 2024 23:59:05 +0000 (UTC) (envelope-from jo@durchholz.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=durchholz.org header.s=default2202 header.b=aLO3Jz6A; dmarc=none; spf=pass (mx1.freebsd.org: domain of jo@durchholz.org designates 78.46.146.228 as permitted sender) smtp.mailfrom=jo@durchholz.org 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=5XK3EVNiHpxfLtVJMad8tsj6mpBBeOthAIvQ5XyKN/g=; b=aLO3Jz6AUUWvw6rQ1JiNVxExSs RviQjvfuPUNKRs+/sfL5sdBl0P22oRpwfHRTadhdFhzOPPvu0722yFdgPFdIwGKtwn8s0ndBU61nM mOFGHjSPPyXXan/Sp+83XBy4ZLUkjcC8srbgEhc+Kfn7QxMIKSeHU6WA50OjVvcqNZvcg/GyzIQyP snnM2Y4VPSI2cCfPv5KHLsh/hcKUfQw2TT3qrGfpRMlyXaZiNkiwkqbure33aE3MhSCWYCE0JMX+O Duh2EARbUpZA8Sowi6pGjopv6rQ3o0mrjbPSLjdgM/UHKP6jlKXCxA+KpfeKJL9tHszKgUkj/ElU0 3uhu+ScQ==; Received: from sslproxy06.your-server.de ([78.46.172.3]) by www382.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rYxFI-000F8p-1J for virtualization@freebsd.org; Sun, 11 Feb 2024 00:58:56 +0100 Received: from [81.221.201.210] (helo=[192.168.178.48]) by sslproxy06.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rYxFH-0002HF-TV for virtualization@freebsd.org; Sun, 11 Feb 2024 00:58:55 +0100 Message-ID: <60f81e4d-8117-4410-b76b-e4ce3e076379@durchholz.org> Date: Sun, 11 Feb 2024 00:58:55 +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: Re: Contributing the build of a KVM image To: virtualization@freebsd.org References: <8d266dd2-5ebc-40db-995f-4a4bfb9707eb@nomadlogic.org> Content-Language: en-US From: Jo Durchholz In-Reply-To: <8d266dd2-5ebc-40db-995f-4a4bfb9707eb@nomadlogic.org> 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/27181/Sat Feb 10 10:34:05 2024) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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:+] X-Rspamd-Queue-Id: 4TXSP51jDYz4rrF Hi Pete, hi all, thanks for the info! Onwards to the next question: What would be the right place to ask questions about how to run `make`? In case this is already the right place, here they are: 1) I'm worried that make will write files to directories that I'm not aware of, or even overwrite stuff it has no business overwriting. How to I make sure that it does not write anywhere except ~/projects/freebsd (which is the place where I want to experiment with the freebsd build)? 2) I want to build the Vmware Vagrant file and its dependencies; what would the correct make target be? (I tried to figure it out but gave up when I saw it's include files; I don't know what to look for when figuring out from where they might be called.) 3) I need to run make on a Linux box. I'm aware of make.py; is there anything specific I need to consider when building Vagrant files? In particular, I'm vaguely worried that something inside the Makefiles will want to install FreeBSD binaries, which would fail but I'm not sure how much damage a failing build process might do? (Probably nothing, but since the Vagrant stuff is in a "release" directory, this might be a less well tested part of the build process, so better ask rather than be sorry.) Regards, Jo On 30.01.24 01:28, Pete Wright wrote: > > On 1/29/24 14: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'd suggest filing a bug first, along with a patch if you have one: > https://bugs.freebsd.org/bugzilla/ > > depending on the complexity of changes developers may ask for you to > start a review in phabricator: > https://wiki.freebsd.org/Phabricator > > if you'd like to get more eyes on this it may be worth sending a message > to freebsd-hackers@ or freebsd-current@ > > > -pete >