[SOLVED] will 64bit ARMv8 AArch64/ARM64 "current" become stable?

drmozes · 04-19-2023, 01:10 PM

Quote:

Originally Posted by drmozes

Ah yes. The change I submitted duplicated x86_64's settings.

Heinz has merged the changes into the template build scripts for us.
I don't know how build problems that users cannot resolve should be handled though: posting the problem here is always an option, then feeding back to the maintainer on the Slackbuilds devel mailing list.

SCerovec · 04-19-2023, 02:57 PM

Quote:

Originally Posted by jloco

I saw your post in ponce’s thread mentioning lua53 which builds fine for me. But I’d be interested in what’s failing to build for you. Most of the scripts should work as-is, providing you’ve added aarch64 to them. But there is the occasional oddball or extremely old software that needs extra help. I wish sbo would just add aarch64 but they worry about not being able to support (though things seems rarely tested anyway). I for one, would love to hear what you’re having problems with.

# sboinstall lua53

Code:

cd src && make linux
make[1]: Entering directory '/tmp/SBo/lua-5.3.4/src'
make all SYSCFLAGS="-DLUA_USE_LINUX" SYSLIBS="-Wl,-E -ldl -lreadline -lncurses"
make[2]: Entering directory '/tmp/SBo/lua-5.3.4/src'
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lapi.o lapi.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lcode.o lcode.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lctype.o lctype.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ldebug.o ldebug.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ldo.o ldo.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ldump.o ldump.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lfunc.o lfunc.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lgc.o lgc.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o llex.o llex.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lmem.o lmem.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lobject.o lobject.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lopcodes.o lopcodes.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lparser.o lparser.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lstate.o lstate.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lstring.o lstring.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ltable.o ltable.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ltm.o ltm.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lundump.o lundump.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lvm.o lvm.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lzio.o lzio.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lauxlib.o lauxlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lbaselib.o lbaselib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lbitlib.o lbitlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lcorolib.o lcorolib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ldblib.o ldblib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o liolib.o liolib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lmathlib.o lmathlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o loslib.o loslib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lstrlib.o lstrlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o ltablib.o ltablib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lutf8lib.o lutf8lib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o loadlib.o loadlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o linit.o linit.c
ar rcu liblua5.3.a lapi.o lcode.o lctype.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o lbitlib.o lcorolib.o ldblib.o liolib.o lmathlib.o loslib.o lstrlib.o ltablib.o lutf8lib.o loadlib.o linit.o 
ranlib liblua5.3.a
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o lua.o lua.c
gcc -std=gnu99 -o lua5.3   lua.o liblua5.3.a -lm -Wl,-E -ldl -lreadline -lncurses 
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX    -c -o luac.o luac.c
gcc -std=gnu99 -o luac5.3   luac.o liblua5.3.a -lm -Wl,-E -ldl -lreadline -lncurses 
make[2]: Leaving directory '/tmp/SBo/lua-5.3.4/src'
make[1]: Leaving directory '/tmp/SBo/lua-5.3.4/src'
cd src && mkdir -p /tmp/SBo/package-lua53/usr/bin /tmp/SBo/package-lua53/usr/include/lua5.3 /tmp/SBo/package-lua53/usr/lib /tmp/SBo/package-lua53/usr/man/man1 /tmp/SBo/package-lua53/usr/share/lua/5.3 /tmp/SBo/package-lua53/usr/lib/lua/5.3
cd src && install -p -m 0755 lua5.3 luac5.3 /tmp/SBo/package-lua53/usr/bin
cd src && install -p -m 0644 lua.h luaconf.h lualib.h lauxlib.h lua.hpp /tmp/SBo/package-lua53/usr/include/lua5.3
cd src && install -p -m 0644 liblua5.3.a /tmp/SBo/package-lua53/usr/lib
cd doc && install -p -m 0644 lua.1 luac.1 /tmp/SBo/package-lua53/usr/man/man1
/usr/bin/ld: lauxlib.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `stderr@@GLIBC_2.17' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: lauxlib.o(.text+0x394): unresolvable R_AARCH64_ADR_PREL_PG_HI21 relocation against symbol `stderr@@GLIBC_2.17'
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
Failures:
  lua53: lua53.SlackBuild return non-zero

FWIW

SCerovec · 04-19-2023, 03:04 PM

Quote:

Originally Posted by drmozes

Hehe, that's basically what it is - and occasionally you'll need to wash the bed sheets at a high temperature on a long cycle ;-)
A HWM custodian is described here.
Slackware ARM is built to support new HWMs easily. Initially it's labor intensive but once we merge the support into OS, over the long term it's a case of maintaining the Kernel module loader script, and testing the support on a monthly basis.
As we merge in the changes for the HoneyCombLX2 I'll be updating the HWM integration documentation. I also need to merge a number of patches for the Installer back to Patrick so I can make available the ARM installer build system, but this won't hold anybody up.

Slackware ARM isn't aiming at broad coverage of Hardware Models because maintaining the quality of the OS and documentation is unsustainable with the small development team (me and Brent) at scale: the idea is that there are a handful of useful HWMs that work as well as possible using the upstream materials, which serve as a reference that the community can use to support others and contribute those changes back if they wish.

I myself too couldn't agree more about not aiming for a broad coverage.

IMHO the rk3588 and rk3588s are the good candidates accounting for the overall performance and options, and maybe the A311D/S922X - everything else is just far behind or simply not worth the hassle.

If You would accept me for one, i think i could fulfill the Custodian duty for the Rock5, but there will be delays with bed sheet washing and cycling - knowing me

Is there a club with meeting to attend to?

jloco · 04-19-2023, 11:45 PM

Quote:

Originally Posted by SCerovec

# sboinstall lua53

Code:

/usr/bin/ld: lauxlib.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `stderr@@GLIBC_2.17' which may bind externally can not be used when making a shared object; recompile with -fPIC

FWIW

This line stating the "recompile with -fPIC" tells me that maybe you haven't added the

Code:

elif [ "$ARCH" = "aarch64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"

to the SlackBuild. Try defining that and try again. I've just built 5.3.4 and 5.3.6 and they both build without error on my machine.

I also have a sort of fork of SBo based on Ponce's repo for software I'm attempting to build and verify things on aarch64. I basically follow the SBo defaults but ensure scripts work on aarch64 properly which I have lua 5.3.6 on here. It's not a complete copy of SBo, it's just software I've verified building and running on my aarch64 machines currently. (It also don't even have all my own scripts on it) but it does have a rather complete sway desktop buildable. It's not really for public consumption, but the script there can be used in place of the SBo script, and it should work for you.

jloco · 04-19-2023, 11:55 PM

Quote:

Originally Posted by drmozes

Heinz has merged the changes into the template build scripts for us.
I don't know how build problems that users cannot resolve should be handled though: posting the problem here is always an option, then feeding back to the maintainer on the Slackbuilds devel mailing list.

Maybe a sticky thread like Ponce's but for aarch64?

That should be good for new additions to SBo, but I wonder about existing software. I'm not sure how to approach that though. Option is always there to do PRs on Ponce's repo (but not sure if any of that actually makes it back to SBo?) It seems like maybe a good sed/grep combo (not my forte) could add it to most existing scripts on the repo. I've just always added it to any slackbuild I make, their stance has always been if I can support it, then it's ok with them. But retro-fitting the repo with support could be a long process either way.

Good news though for the future, exciting to see something happening!

drmozes · 04-20-2023, 05:09 AM

Quote:

Originally Posted by jloco

Maybe a sticky thread like Ponce's but for aarch64?

This has been a good discussion.

I've knocked this page up and will link to it from the install guides later. This should enable most of you to build packages from SBo easily.
We can have a sticky thread on this forum if it helps - I'll ask the mods to do it later once you guys have checked that doc.

Cheers

drmozes · 04-21-2023, 03:16 AM

Quote:

Originally Posted by SCerovec

IMHO the rk3588 and rk3588s are the good candidates accounting for the overall performance and options, and maybe the A311D/S922X - everything else is just far behind or simply not worth the hassle.

If You would accept me for one, i think i could fulfill the Custodian duty for the Rock5, but there will be delays with bed sheet washing and cycling - knowing me

That's fine, this is *Slack*ware after all.

Quote:

Is there a club with meeting to attend to?

That sounds terribly well organised. No, Slackware just unfolds.

I've created a new thread for this and let's take it from there.