From nobody Mon Jan 6 23:21:18 2025 X-Original-To: freebsd-arm@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 4YRqtj4pdNz5kP87 for ; Mon, 06 Jan 2025 23:21:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRqth4tWVz40Nv for ; Mon, 6 Jan 2025 23:21:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 506NLJsq034210 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Jan 2025 15:21:19 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 506NLIad034209; Mon, 6 Jan 2025 15:21:18 -0800 (PST) (envelope-from fbsd) Date: Mon, 6 Jan 2025 15:21:18 -0800 From: bob prohaska To: Warner Losh Cc: freebsd-arm@freebsd.org Subject: Re: Buildworld fatal error: 'byteswap.h' file not found on armv7 Message-ID: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4YRqth4tWVz40Nv X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] On Mon, Jan 06, 2025 at 01:15:55PM -0700, Warner Losh wrote: > Please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273736 for one > possible solution, > though it focuses on 13.x. > It doesn't seem to make a difference. Right now ./tools/build/cross-build/include/common/osreldate.h contains (apart from disclaimers): #pragma once #define __FreeBSD_version 0 -----the original file ended here----- #ifndef __APPLE__ #if __FreeBSD_version >= 1400079 || (__FreeBSD_version < 1400000 && __FreeBSD_version >= 1204600) #define HAVE_BYTESWAP_H 1 #endif #endif I tried commenting out the #define __FreeBSD_version 0 line thinking it might defeat the test, to no effect. I also dithered the last conditional value above and below the actual value of 1204500 to see if exact equality mattered. Finally I commented out the entire test, leaving only #define HAVE_BYTESWAP_H 1 to no avail. Unless I've done something really obvious wrong it's probably better to start over with a new snapshot so long as they're available and bootable. Thanks for writing! bob prohaska > > On Mon, Jan 6, 2025 at 1:08 PM bob prohaska wrote: > > > As an experiment I've tried to build -current and 14.2-stable > > on a Pi2 v1.1 running 12.4-stable. I know it's not considered > > good practice to hop that far, but I wanted to see for myself. > > > > I thought it would at least compile, since I have another Pi2v1.1 > > which has been tracking -current and is presently up-to-date. > > > > However, the build fails in both buildworld and toolchain, with > > /usr/src/contrib/file/src/apprentice.c:54:10: fatal error: 'byteswap.h' > > file not found > > #include > > ^~~~~~~~~~~~ > > > > The missing file is actually present: > > root@pelorus:/usr/src # find . -name byteswap.h -depth -print > > ./contrib/llvm-project/libcxx/include/__bit/byteswap.h > > ./contrib/ofed/include/byteswap.h > > ./include/byteswap.h > > root@pelorus:/usr/src # > > > > It's a little hard to see how using 12.4 might cause this sort of error. > > The source directory is a fresh clone. > > > > Is this an expected failure mode? If there's an easy workaround I'd like > > to try, but if not it's no big deal, I'll just reflash the microSD. > > > > Thanks for reading, and any insights. > > > > bob prohaska > > > > > > > > > > > >