On 5/6/24 3:19 pm, Nuno Teixeira via slurm-users wrote:
Fixed with:
[...]
Thanks and sorry for the noise as I really missed this detail :)
So glad it helped! Best of luck with this work.
--
Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
--
slurm-users mailing list -- slu
(...)
Fixed with:
+.elif ${ARCH} == aarch64
+ ${FIND} ${LLD2FIX:C|^|${WRKSRC}/src/|} -name Makefile.in |
${XARGS} \
+ ${REINPLACE_CMD} -e 's|-r -o|-r -m aarch64elf -o|'
Thanks and sorry for the noise as I really missed this detail :)
Cheers,
Nuno Teixeira escreveu (seg
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|^|${WRKSR
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:
/
On Mon, 2024-05-06 at 11:38:30 +0100, Slurm users wrote:
> Hello,
>
> I instructed port to use binutils from ports (version 2.40 native) instead
> of base:
>
> `/usr/local/bin/ld: unrecognised emulation mode: elf_aarch64`
>
> ```
> /usr/local/bin/ld -V |grep aarch64
>aarch64cloudabi
>aar
Hello,
I instructed port to use binutils from ports (version 2.40 native) instead
of base:
`/usr/local/bin/ld: unrecognised emulation mode: elf_aarch64`
```
/usr/local/bin/ld -V |grep aarch64
aarch64cloudabi
aarch64cloudabib
aarch64elf
aarch64elf32
aarch64elf32b
aarch64elfb
On 5/4/24 4:24 am, Nuno Teixeira via slurm-users wrote:
Any clues?
> ld: error: unknown emulation: elf_aarch64
All I can think is that your ld doesn't like elf_aarch64, from the log
your posting it looks that's being injected from the FreeBSD ports
system. Looking at the man page for ld on
