Re: Buildworld fatal error: 'byteswap.h' file not found on armv7

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 <[email protected]> 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 <byteswap.h>
> >          ^~~~~~~~~~~~
> >
> > 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
> >
> >
> >
> >
> >
> >