[OpenAFS] question about openafs 1.8.2 on aarch64

[Benjamin Kaduk]

On Wed, Feb 13, 2019 at 10:31:32PM -0500, Gary Gatling wrote:
> Hi. Thanks so much for replying. I was actually looking at this again
> tonight, for some odd reason I can't explain.
> 
> It was so stupid. I did not set the sysname. I have added:
> 
> %ifarch aarch64
> %define sysname aarch64_linux26

I think you want "arm64_linux26" -- see src/config/param.arm64_linux26.h

-Ben

> %endif
> 
> 
> I get a different error now:
> 
> echo 'char* AFSVersion = "openafs '$VERSION'";'
> >>AFS_component_version_number.c.NEW && \
> if cmp AFS_component_version_number.c.NEW AFS_component_version_number.c >
> /dev/null 2>&1 ; then : ; else \
> mv AFS_component_version_number.c.NEW AFS_component_version_number.c ; fi )
> rm -f AFS_component_version_number.c.NEW
> make[4]: Leaving directory
> '/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config'
> gcc    -g -O   -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config
> -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/include -I. -I.      -o
> config.o -c config.c
> gcc    -g -O   -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config
> -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/include -I. -I.      -o mc.o -c
> mc.c
> gcc   -L/home/gsgatlin/redhat/BUILD/openafs-1.8.2/lib
> -L/home/gsgatlin/redhat/BUILD/openafs-1.8.2/lib -g -O     -g -O
>  -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config
> -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/include -I. -I.      -o config
> config.o mc.o
> gcc    -g -O   -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config
> -I/home/gsgatlin/redhat/BUILD/openafs-1.8.2/include -I. -I.
>  -L/home/gsgatlin/redhat/BUILD/openafs-1.8.2/lib
> -L/home/gsgatlin/redhat/BUILD/openafs-1.8.2/lib -g -O   \
> -o mkvers ./mkvers.c
> make[3]: *** No rule to make target 'param.aarch64_linux26.h', needed by
> 'param.h.new'.  Stop.
> make[3]: Leaving directory
> '/home/gsgatlin/redhat/BUILD/openafs-1.8.2/src/config'
> make[2]: *** [Makefile:146: config] Error 2
> make[2]: Leaving directory '/home/gsgatlin/redhat/BUILD/openafs-1.8.2'
> make[1]: *** [Makefile:650: build] Error 2
> make[1]: Leaving directory '/home/gsgatlin/redhat/BUILD/openafs-1.8.2'
> make: *** [Makefile:35: all_nolibafs] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.ZbdvPL (%build)
> 
> Any idea what that means?  :)
> 
> *** No rule to make target 'param.aarch64_linux26.h', needed by
> 'param.h.new'.  Stop.
> 
> I am running this inside qemu on a intel dell laptop.
> 
> Thanks a lot for any ideas you might have. I can upload any makefiles to
> pastebin.
> 
> 
> 
> On Wed, Feb 13, 2019 at 9:55 PM Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> > On Wed, Feb 13, 2019 at 08:11:44AM -0500, Gary Gatling wrote:
> > > Hello.
> > >
> > > When I try to compile openafs on fedora 29 on x86_64 it works fine but
> > when
> > > I try to compile openafs on fedora 29 on aarch64 I get an error:
> > >
> > > mkdir -p /builddir/build/BUILD/openafs-1.8.2/include/hcrypto
> > > mkdir -p /builddir/build/BUILD/openafs-1.8.2/include/opr
> > > mkdir -p /builddir/build/BUILD/openafs-1.8.2/lib
> > > cd src && cd config && make all
> > > make[3]: Entering directory
> > '/builddir/build/BUILD/openafs-1.8.2/src/config'
> > > make[3]: Leaving directory
> > '/builddir/build/BUILD/openafs-1.8.2/src/config'
> > > Makefile:68: *** mixed implicit and normal rules.  Stop.
> > > make[2]: *** [Makefile:146: config] Error 2
> > > make[2]: Leaving directory '/builddir/build/BUILD/openafs-1.8.2'
> > > make[1]: Leaving directory '/builddir/build/BUILD/openafs-1.8.2'
> > > make[1]: *** [Makefile:650: build] Error 2
> > > make: *** [Makefile:35: all_nolibafs] Error 2
> > > error: Bad exit status from /var/tmp/rpm-tmp.B61XCV (%build)
> > >
> > > I get this error on RHEL 8 beta (aarch64) also in "mock."
> > >
> > > Has anyone else run into this before? Was just curious if there was a
> > known
> > > solution. The problem seems to be in the Makefile on line 68 with "mixed
> > > implicit and normal rules" although maybe that is not the real problem?
> >
> > Hi Gary,
> >
> > I don't recall haring about such errors previously.  The direct debugging
> > techniques would seem to require examining the apparently problematic
> > Makefile; would you be able to post the generated src/config/Makefile
> > somewhere?
> >
> > Thanks,
> >
> > Ben
> >