From nobody Fri Sep 13 22:37:13 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 4X58M2124bz5W7q8 for ; Fri, 13 Sep 2024 22:37:18 +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 4X58M12Gvqz4Vnv for ; Fri, 13 Sep 2024 22:37:17 +0000 (UTC) (envelope-from dclarke@blastwave.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=C812G8ax; 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 48DMbDBR082425 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 13 Sep 2024 18:37:15 -0400 (EDT) (envelope-from dclarke@blastwave.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=blastwave.org; s=default; t=1726267035; bh=UERHL78yvEzal9Lu1gjd+2Zat5VTdf5IsjefYnvamfI=; h=Date:Subject:To:References:From:In-Reply-To; b=C812G8ax8fahmxpOmV5UUhO6UvZ9NmgIhyJNFefdLeLXqc5k1dhEQA35m5QRidrv8 FTM5FjC2OG6ljdsCIPkl0lUwGJJKli6a9rcHNHYReDo6IVtCeTrkCndMRuOOJyIAoy awJbk6LhsY0v43qNMinN/OrSWM5aM6PKf3PLpGVXxQsdknKjGKwDmmycAKCpZFLTjb v4b1+YTfMM6x+PpddH9Aqbipj/1kyNfnyqldY7L3vgEzAfg7sAG3RENRy8HSorOC6i j9upYhRQR+yPHQakDA9mPOimRZZoqSg1tfYdMRG0cz6MiXaC5YFGMIWYFem39QrI5m ni4zqG26kZUQg== Message-ID: <8e18d3a5-13ea-44ba-a030-5aac6314496d@blastwave.org> Date: Fri, 13 Sep 2024 18:37:13 -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 Subject: Re: Why this message "kernel is missing COMPAT_FREEBSD11" Content-Language: en-CA To: riscv@freebsd.org References: <84f1f8e5-a375-4f2b-b9f8-8016fd60c186@blastwave.org> From: Dennis Clarke Organization: GENUNIX In-Reply-To: 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: 48DMbDBR082425 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:c]; 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:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; 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: 4X58M12Gvqz4Vnv On 9/13/24 18:09, Jessica Clarke wrote: > On 13 Sep 2024, at 23:03, Dennis Clarke wrote: >> >> >> Dear RISC-V types : >> >> I have been watching my SiFive board grind away slowly with >> poudriere for a while and today I saw this message about emacs: >> >> [01] [00:10:20] Skipping editors/emacs@full | emacs-29.4,3: Dependent port lang/rust | rust-1.81.0 failed >> >> >> This of course will tell me that something went wrong when trying to >> build rust. Somewhere. Somehow. Thankfully there is a detailed log file >> on this Friday the 13th wherein I see : >> >> >> =================================================== >> ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 >> ===> Configuring for rust-1.81.0 >> ===> FreeBSD 10 autotools fix applied to /wrkdirs/usr/ports/lang/rust/work/rustc-1.81.0-src/vendor/libssh2-sys-0.3.0/libssh2/config.rpath >> ===> FreeBSD 10 autotools fix applied to /wrkdirs/usr/ports/lang/rust/work/rustc-1.81.0-src/vendor/libssh2-sys-0.2.23/libssh2/config.rpath >> Bad system call >> => Sanity check failed: kernel is missing COMPAT_FREEBSD11 >> => Aborting build >> *** Error code 1 >> >> Stop. >> make: stopped making "configure" in /usr/ports/lang/rust >> =>> Cleaning up wrkdir >> ===> Cleaning for rust-1.81.0 >> build of lang/rust | rust-1.81.0 ended at Fri Sep 13 02:04:27 UTC 2024 >> build time: 00:10:20 >> !!! build failure encountered !!! >> >> >> Well gee. Does this mean I need to stop everything and do a build of the >> kernel with some magic config variable "COMPAT_FREEBSD11" in some magic >> file somewhere? > > See https://github.com/rust-lang/rust/issues/92466 and > https://github.com/rust-lang/rust/issues/89058. > > Jess Thank you once again for the pointers. At first glance this appears to be a serious compatibility issue in the rust world. I guess I could spend and hour or so to read top to bottom everything in both of those bug reports. As I say, at first glance, it seems to be a brick wall. I'll think about the situation on this Friday the 13th. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken