Hello,

I too think this the cause and I really missed it:

.if ${ARCH} == powerpc64le
        ${FIND} ${LLD2FIX:C|^|${WRKSRC}/src/|} -name Makefile.in | ${XARGS}
    \
                ${REINPLACE_CMD} -e 's|-r -o|-r -m elf64lppc -o|'
.elif ${ARCH} == powerpc64
        ${FIND} ${LLD2FIX:C|^|${WRKSRC}/src/|} -name Makefile.in | ${XARGS}
    \
                ${REINPLACE_CMD} -e 's|-r -o|-r -m elf64ppc -o|'
.else
        ${FIND} ${LLD2FIX:C|^|${WRKSRC}/src/|} -name Makefile.in | ${XARGS}
    \
                ${REINPLACE_CMD} -e 's|-r -o|-r -m elf_${ARCH} -o|'

I will adjust it and see build result.

Thanks,

Christopher Samuel via slurm-users <slurm-users@lists.schedmd.com> escreveu
(segunda, 6/05/2024 à(s) 14:35):

> On 5/6/24 6:38 am, Nuno Teixeira via slurm-users wrote:
>
> > Any clues about "elf_aarch64" and "aarch64elf" mismatch?
>
> As I mentioned I think this is coming from the FreeBSD patching that's
> being done to the upstream Slurm sources, specifically it looks like
> elf_aarch64 is being injected here:
>
> /usr/bin/sed -i.bak -e 's|"/proc|"/compat/linux/proc|g'  -e
> 's|(/proc)|(/compat/linux/proc)|g'
>
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/slurmd/slurmstepd/req.c
> /usr/bin/find
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/api
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/plugins/openapi
>
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/sacctmgr
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/sackd
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/scontrol
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/scrontab
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/scrun
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/slurmctld
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/slurmd/slurmd
> /wrkdirs/usr/ports/sysutils/slurm-wlm/work/slurm-23.11.6/src/squeue
> -name Makefile.in | /usr/bin/xargs       /usr/bin/sed -i.bak -e 's|-r
> -o|-r
> -m elf_aarch64 -o|'
>
> So I guess that will need to be fixed to match what FreeBSD supports.
>
> I don't think this is a Slurm issue from what I see there.
>
> All the best,
> Chris
> --
> Chris Samuel  :  http://www.csamuel.org/  :  Berkeley, CA, USA
>
>
> --
> slurm-users mailing list -- slurm-users@lists.schedmd.com
> To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
>


-- 
Nuno Teixeira
FreeBSD UNIX:  <edua...@freebsd.org>   Web:  https://FreeBSD.org
-- 
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com

Reply via email to