From nobody Thu Aug 29 17:43:23 2024 X-Original-To: riscv@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 4WvpY56vJHz5THRn for ; Thu, 29 Aug 2024 17:43:37 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WvpY51Qxzz59FQ for ; Thu, 29 Aug 2024 17:43:37 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=U+yuUIve; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 47THhODi059825 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Thu, 29 Aug 2024 13:43:34 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1724953414; bh=DbZdEn2BfGB8dVW9Qt7xDqC0si7VFR1MhSMTOAVuqvw=; h=Date:To:From:Subject; b=U+yuUIvetZ6/GOGsfKhXtvyJySVWqlbrQFQoVMKD7LLh6MXftt01QkbIU+RB8KfPC owKbrG7tzMcdVqc6UUyVwsShIdh+auFVW6nKS0ZqleQv0nnsz/IEe7vGDdUOmCxh5h 784X8j/p+SBFoLU/K5zIu1daGATy+XVYnyz8VCwD2UfdASiilVAtPv7Mng+MU5cP2g rdFLow6/BjD6cGnl4TOM6GdpI6Svd1ZwZ5Fos7XyTweCS7nvzHjJfYEtfdvjF0zQmU d0QFulX4HLaMrIMU8eIu4KTk/wmlyRAYfZnD0w+rwLy/4rpDcrltY8PrhBTavwSYaq ZFHbsIS6lB4IA== Message-ID: Date: Thu, 29 Aug 2024 13:43:23 -0400 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: riscv@FreeBSD.org Content-Language: en-CA From: Dennis Clarke Subject: Question about the docs at https://wiki.freebsd.org/riscv/ports Organization: GENUNIX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 47THhODi059825 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.69 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[blastwave.org:+]; MLMMJ_DEST(0.00)[riscv@FreeBSD.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4WvpY51Qxzz59FQ Dear RISC-V user types : I have a package server that does daily builds for amd64 with jails setup for 13.3 and 14.1 and of course CURRENT. This works really well and generally gets the job done for all of KDE5 and LXDE and XFCE plus some database tools and other tidbits. Roughly 3 or 4 hours for 1800 packages and that serves me well. Regarding the docs for riscv64 package builds at : https://wiki.freebsd.org/riscv/ports I see that it says we need qemu-user-static built and installed and then I *may* be able to setup a riscv64 jail? My plan is to try and get a 14.1 jail as well as a CURRENT jail from the sources I have built the host with. However qemu is just horribly slow. So terrible that I may have to wait a week to get that jail built. So therefore : (1) are those docs still reasonable ? (2) is it just a waste of time ? I have the little SiFive UnMatched board which is supposed to all "just work" per https://wiki.freebsd.org/riscv#Supported_Platforms and I have a Samsung 990 SSD M.2 thing on it. Will it be able to run proper poudriere package builds without too much horror ? -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken From nobody Fri Aug 30 15:43:34 2024 X-Original-To: riscv@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 4WwMrH3Dhkz5Mn27 for ; Fri, 30 Aug 2024 15:43:43 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WwMrH2blzz47vY; Fri, 30 Aug 2024 15:43:43 +0000 (UTC) (envelope-from mhorne@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725032623; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=XpyPQgEOENpW2syuBixWPBIVTRpYFpgJ8wUVL7v94M8=; b=KeZi0tcTcIVKf+PaOjf8HOJZ4uihYqT7VO5CLCPYsmiM8cS6Why53vElpzjrL1u2eYM9C+ FOrm73oLLLLMnQKfNlzjnyev5qWr0gHtlN84UJoog1xfgtTa1ueWDq323mrwP58+4c5DY7 CtyUSuIChS21Q2R8LQ8nRuCguutPPAEymFU9ObBcVbTL6VgU7c/X4rRRovdZHsPssKtJ2q KA0B4KAg172tS9lplmmRBZmX6wZH7KC9ihZSZ/DU1YN8NlI6dcnOxnGVJi8dLmLuk+CmLA h9K2T+VHDn0Pj6MqDy8lY5IjtFh+vBIGNzkdJCX1yzB4fr655dP+knd8uo9zgw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1725032623; a=rsa-sha256; cv=none; b=Miq4TcDmxIVOuanKgWx5SOdViCfOmETmlQZz/XVQmSIOIsNX43uM1KeJRfuwnXZnoAufB0 klvM06qo0P/ep5cLwbfzgtziYa6QDZt0+lI3NMDcRE7CRDovajvtMdLShpomYnWEqjVEAn CWt2CdWBkVcx025glrEwVeLssMBKvys9DxX+tPNujIhZmRMzixwPRWCh0PSUP0p2mc5OBH wa40dkhKsHNU/28uZl/yU5nUZtzYCJpqa4/c1K6OkYyox91F4v7YlagQmBkINSjMx+0C/r ws/F+BSriXT2rZBuxrvHvwKJPFoPOE8CFBno64MwT21Nj0XJ+zARIs9Kd2bjwQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1725032623; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=XpyPQgEOENpW2syuBixWPBIVTRpYFpgJ8wUVL7v94M8=; b=i3LXlUO7KsyUkTpjF3B55Pc2sUwhDLb82qaj0UNvjXQWgP/LYL+0ubBVMOkYuZstsvOHVs 6sABjzzWQeLXNqWoelrT9oa3UPXFDdlh2l+ROJYVTl5M3ztsiMl/1nbLVDjii/vmjqYYCC rPKvDre9Hnn6/ko9FFhugX1TJJiK74F/08URrF8dqSbf/Mg+ELoFCMjSP8A02wc86PbfAg 4P07IDcYBHFR27J7B3X5Mj9h+rlzWfizshW6sVNN7NkKXtaN8MrAvxxO1LBJwTP3VT+Ogl PyiogXHBoU6OmnStbG4GPHKhzLhJ8eQfuk2gZ0WKYdJqiI1IpLOTo7KOxoYFKg== Received: from [192.168.2.217] (hlfxns018gw-134-41-188-50.dhcp-dynamic.fibreop.ns.bellaliant.net [134.41.188.50]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WwMrH1P1Lz18jy; Fri, 30 Aug 2024 15:43:43 +0000 (UTC) (envelope-from mhorne@freebsd.org) Message-ID: <761a4270-8afe-4f50-b32a-3706b4f8ae5e@freebsd.org> Date: Fri, 30 Aug 2024 12:43:34 -0300 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Question about the docs at https://wiki.freebsd.org/riscv/ports To: Dennis Clarke , riscv@FreeBSD.org References: Content-Language: en-CA From: Mitchell Horne Autocrypt: addr=mhorne@freebsd.org; keydata= xsBNBFyS2dQBCADdiXBG8hBVLmYbxu7aSzbwLwUf3HkGFz3rooS1kwyy+SfmjZ4UKNnl9WMx WKrJ7OAZpiNH6bLQ5nsqfx09OnpWL8c/QuPbhNdUywQoqqYpRI0K8GEn//nS9Gs0KTYwVpWb XlrzP+jf3Uh/9L5mcQmStLIH4zaaqMYHW+pMuPrvBmLIHTvLj2QjOkxslrcUdord9uvxe5Ht LU8RuTpQpHOKz705Z9/v7twFdi2HtKzpLwO6SzVyu351di1J+GihsVpcT5josQV5cHbIP3Un x+kmtKBEEc/jl/zBglF7ruWUtwgbryID+2ZPEaO1Mj+RResX4LFVMusq3uUpWRb5WJXxABEB AAHNI01pdGNoZWxsIEhvcm5lIDxtaG9ybmVARnJlZUJTRC5vcmc+wsCUBBMBCgA+AhsDBQsJ CAcCBhUKCQgLAgQWAgMBAh4BAheAFiEEkp/cYPcfabAiQvACi/gnTOdUid8FAmIyDpUFCQtC z0EACgkQi/gnTOdUid8IsQf+N8IptrrCgifT5Z0/WUVFfnHThFOKf4zBjaGswsIM8+VKsKnF 15jCWHODUHP6s+dcQ4nQi81PHPsnMfBSkGPvN/X3ess2/1KUVkH+6tAJbqXDjXhD8HT+i0NM QEFIXlLnotpgIKW3yOHjKv3ZvKw9LCvUjyNY9vOJmLk/6AbbkFh+INo65nXtQWb/hM5FVEHW S+zUoU8AqZRJoVAQfj9wmIfg/HdsxeDGKL0zkv5AwKpccvb8VJNGJbCVMgoy5uQYcUeXxcie cg0VlbFLshNQTfyhVQ85vyuHahARrUWs/k8KiYODoBnW1ChtyF8yM6VZTzSYx7pINqPq2YZy i/Htd87ATQRcktnUAQgA3zt4M4ecoQqfxpjliNLujt9klDqvmkJvWmzMuMXdzlPgGRJ0doio 9YIeEdkOt6xN0pPTK/ReCZ8WqFQ8zo23u1pwGuo0CnR58XF19wyxyUuKu/PHbt+56mC8tNHm AXsMyXQmlDqWvn/WzLY7euNRtNS4QQIwtxfM5EC4GGa5KQwxn0kM7dkUSOE/cxr+/kNbHHzb gagZR4cnNUqtPPr3dYXcibCTzgz96Lyt3/qMLXX9RTBRzu+O6E+byxWOe8ar/ZlwY2b4wTQG mhgNttkSxKtxMpZnd8+DGV/bI1P5Ct/K2GeCwNyupQGON5ymn6o7jTch+qmFX0ItkBWO4zn4 9QARAQABwsB8BBgBCgAmAhsMFiEEkp/cYPcfabAiQvACi/gnTOdUid8FAmIyDtwFCQtCz4gA CgkQi/gnTOdUid/i5gf/aQ75pJR4TJFM2vVVr6PDIwTdl0b5EchB4w4s4g/zE84XNbMOQanb BginLYEhAacLQVAvM3XdvUEhwrhaMQdjdSEB1krResL3/mbxrtKwdHSMbHA3IS3XdvxFWTB7 P5JjUSPsW6hqgoidbn4w3OxaNHhs45H2b0Nx5QiKcSyepmCZuB52gCEHnEnrdaz8TFQMXOLq 94WbTmZeIjChW3FB61m1gTf0UEFjoZAfTAUB+pbwoCa4AykIeZnDC19vjsruVU9Gy5rLglwd bjsZNfXIJGOZNEvdF8FOBwM7DlXx7SYvTJcUNoNJjOKtQ0bYGVgGqYOB/y2mTjVuKeU0eOkN Uw== In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 8/29/24 14:43, Dennis Clarke wrote: > > Dear RISC-V user types : > >     I have a package server that does daily builds for amd64 with jails > setup for 13.3 and 14.1 and of course CURRENT. This works really well > and generally gets the job done for all of KDE5 and LXDE and XFCE plus > some database tools and other tidbits. Roughly 3 or 4 hours for 1800 > packages and that serves me well. > >     Regarding the docs for riscv64 package builds at : > >         https://wiki.freebsd.org/riscv/ports > >     I see that it says we need qemu-user-static built and installed and > then I *may* be able to setup a riscv64 jail?  My plan is to try and get > a 14.1 jail as well as a CURRENT jail from the sources I have built the > host with. However qemu is just horribly slow. So terrible that I may > have to wait a week to get that jail built. So therefore : > I think you misunderstand the use of QEMU here. The jail is not being built inside QEMU. The instructions are for cross-compiling riscv64 packages on an amd64 host. So, a riscv64 jail will be built and installed on the host, including a cross-compiler. QEMU is used in a limited way here, to emulate execution of riscv64 binaries on the host. It is slower than native package building, but faster than full-system emulation. >         (1) are those docs still reasonable ? > These instructions are untouched and untested for a while. They are still generally applicable, but there may be stumbling blocks, I am not sure. >         (2) is it just a waste of time ? > Not completely, but the riscv ports experience is still pretty incomplete and a distance from "just works". So, it depends on how you value spending your time. >     I have the little SiFive UnMatched board which is supposed to all > "just work" per https://wiki.freebsd.org/riscv#Supported_Platforms and > I have a Samsung 990 SSD M.2 thing on it. Will it be able to run proper > poudriere package builds without too much horror ? > I have never tried native poudriere builds on the Unmatched, but I believe some users have with some success. It will (of course) be slow compared to commodity amd64 hardware. Running package builds also stresses the system, and may expose software or hardware instability. So, you can try this, but you will be walking an unmarked path, so to speak. It is fair to expect some minor "horror", but it is possible to build packages. From nobody Sat Aug 31 23:13:45 2024 X-Original-To: riscv@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 4Wx9nD4jTqz5TSFh for ; Sat, 31 Aug 2024 23:13:52 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (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-signature ECDSA (P-256) client-digest SHA256) (Client CN "mail.oetec.com", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wx9nC52Xlz41Mx; Sat, 31 Aug 2024 23:13:51 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=MS7Iw+TT; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org Received: from [172.16.35.3] (pool-99-253-118-250.cpe.net.cable.rogers.com [99.253.118.250]) (authenticated bits=0) by mail.oetec.com (8.17.1/8.17.1) with ESMTPSA id 47VNDkrl031247 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Sat, 31 Aug 2024 19:13:47 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1725146028; bh=t+/eQ5tkqJFk1B3lAUAao359whbTfLsgduzT1MjBc5s=; h=Date:From:Subject:To:References:In-Reply-To; b=MS7Iw+TTnNxypnQRs3pxs6psh6QM2tMb7XT0Bd58prxj4aPaTVDCpxvLEv2p8s6X2 AuGFSeCBwoBVqH06niNqWL2yyX4d9Is1rIKureK93lDbClJhitHdkcFVf9vwTx0FyD pXNUQOEMkYIJR25IV2uEoF7meqFnasE/ncocGStv1ntYbApa28GuzIRV/St9WN9hrB xsUYBeTS9vfC/hBS9K/bGrDIOlqWAOKKhKph3XwRuj+jJO8dfmg3cxT2E8R/NsBQyA GnSKuLjvye+FtQoUDtcBvKn5wftS3XR4HG4zatAuZiSn18caSmeXTro1LuAvUTRmn1 mUN9IGPs3ZI3w== Message-ID: Date: Sat, 31 Aug 2024 19:13:45 -0400 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Dennis Clarke Subject: Re: Question about the docs at https://wiki.freebsd.org/riscv/ports To: Mitchell Horne , riscv@FreeBSD.org References: <761a4270-8afe-4f50-b32a-3706b4f8ae5e@freebsd.org> Content-Language: en-CA Organization: GENUNIX In-Reply-To: <761a4270-8afe-4f50-b32a-3706b4f8ae5e@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-oetec-MailScanner-Information: Please contact the ISP for more information X-oetec-MailScanner-ID: 47VNDkrl031247 X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-From: dclarke@blastwave.org X-Spam-Status: No X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.38 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.69)[-0.688]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; HAS_ORG_HEADER(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[riscv@FreeBSD.org]; DKIM_TRACE(0.00)[blastwave.org:+] X-Rspamd-Queue-Id: 4Wx9nC52Xlz41Mx On 8/30/24 11:43, Mitchell Horne wrote: > > > On 8/29/24 14:43, Dennis Clarke wrote: >> >> Dear RISC-V user types : >> >>      I have a package server that does daily builds for amd64 with jails >> setup for 13.3 and 14.1 and of course CURRENT. This works really well >> and generally gets the job done for all of KDE5 and LXDE and XFCE plus >> some database tools and other tidbits. Roughly 3 or 4 hours for 1800 >> packages and that serves me well. >> >>      Regarding the docs for riscv64 package builds at : >> >>          https://wiki.freebsd.org/riscv/ports >> >>      I see that it says we need qemu-user-static built and installed and >> then I *may* be able to setup a riscv64 jail?  My plan is to try and get >> a 14.1 jail as well as a CURRENT jail from the sources I have built the >> host with. However qemu is just horribly slow. So terrible that I may >> have to wait a week to get that jail built. So therefore : >> > > I think you misunderstand the use of QEMU here. The jail is not being > built inside QEMU. The instructions are for cross-compiling riscv64 > packages on an amd64 host. So, a riscv64 jail will be built and > installed on the host, including a cross-compiler. QEMU is used in a > limited way here, to emulate execution of riscv64 binaries on the host. > It is slower than native package building, but faster than full-system > emulation. > Thank you for the reply. I was able to make some progress in the last few days. However it has been no fun. Really. There was no way at all I could have done much of anything without the fantastic help of Jessica Clarke who gave detailed instructions to get around the land mines in the SiFive UnMatched land. Flashing the darn firmware was a real treat. We needed to use a memory based md0 device and then dd that thing onto the flash. That took hours to find out. I managed to install 15.0-CURRENT onto the SiFive Unmatched and it seems to work. More or less. There are no packages available and so I went ahead with a build in /usr/ports to get "pkg". I have a reasonably beefy AMD64 pkg build server but the mystery is that bizarre qemu_user_static package. It seems to be utterly borked and broken : triton# poudriere jail -c -a riscv.riscv64 -x -j 150rv64 -J 16 \ -D -f t1/poudriere/jails/150rv64 -m git+ssh \ -v main -U 'ssh://anongit@git.FreeBSD.org/src.git' [00:00:00] Cross-building ports for riscv.riscv64 on amd64 requires QEMU [00:00:00] Creating 150rv64 fs at /poudriere/jails/150rv64... done [00:00:00] Checking out the sources with git+ssh...triton# triton# Right ... so what does this thing want from me ? triton# grep 'qemu' /etc/rc.conf qemu_user_static_enable="YES" triton# triton# service qemu_user_static start 'arm' is not unique in activator list usage: binmiscctl command [args...] Add a new binary image activator (requires 'root' privilege): binmiscctl add --interpreter \ --magic [--mask ] \ --size [--offset ] \ [--set-enabled] \ [--pre-open] . . . about a 100 lines of the same stuff over and over and over ... . . Add a new binary image activator (requires 'root' privilege): binmiscctl add --interpreter \ --magic [--mask ] \ --size [--offset ] \ [--set-enabled] \ [--pre-open] Remove a binary image activator (requires 'root' privilege): binmiscctl remove Disable a binary image activator (requires 'root' privilege): binmiscctl disable Enable a binary image activator (requires 'root' privilege): binmiscctl enable Lookup a binary image activator: binmiscctl lookup List all the binary image activators: binmiscctl list triton# So whatever that QEMU static thing is .... well I have no clue. > These instructions are untouched and untested for a while. They are > still generally applicable, but there may be stumbling blocks, I am not > sure. > Based on my experience thus far I will need to write some detailed docs about this process. > > Not completely, but the riscv ports experience is still pretty > incomplete and a distance from "just works". So, it depends on how you > value spending your time. > Thus far it all feels like a prototype on the edge of "working" with a pile of little problems in all directions. From firmware upwards. Even the documentation from SiFive is sketchy. Complete with dip switch settings that are upside down or entirely undocumented. I am so very thankful for Jessica Clarke as there was just no way any user would have a clue how to deal with this board. I even resorted to using my old fluke multimeter just to figure out what those dip switch settings *really* are. At the moment I am trying to build git natively. If that works then I may be able to clone out the sources and try a buildworld etc. However my first attempt at that failed with weird messages about some binary being unrecognizable. An old bug to be sure. > > I have never tried native poudriere builds on the Unmatched, but I > believe some users have with some success. It will (of course) be slow > compared to commodity amd64 hardware. Running package builds also > stresses the system, and may expose software or hardware instability. > > So, you can try this, but you will be walking an unmarked path, so to > speak. It is fair to expect some minor "horror", but it is possible to > build packages. Yes, some minor scary bits. Minor. No open flame or smoke. Yet. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken