Current nodejs and ruby on Apple Silicon fail emerge[solved]

[flysideways]

I was curious if anyone other than me is having problems emerging the current nodejs and ruby on Apple Silicon.

I am having issues, with both, on VMWare Fusion and UTM vm's.

[Banana]

If you could please the commands and output, maybe somone can help

[flysideways]

I'm not seeing the problem. I waited a while to see if subsequent updates might have fixed it.

make.conf https://bpa.st/raw/ALNA

From the VMWare Fusion VM for nodejs:

command and info https://bpa.st/raw/ZGNQ
build log https://bpa.st/raw/XTZA

for ruby:

command https://bpa.st/raw/3HOQ
build log https://bpa.st/raw/7KOQ


Edit to add: They compile with -march reduced to armv8-a. When I started with this MacBook I was using, the then current gcc 12, and some of the extensions invoked by native were causing problems. In the previous cases I had been able to find the offending extensions in the build logs. I don't see them now. I'm now using gcc 14 and the set of packages that fail to build using native is much smaller than before. I need more time to discover which extensions are causing the failures.

[gentoo_ram]

You have unstable ~arm64 turned on globally. Not sure if that's part of the problem.

[flysideways]

Code: Select all

resolve-march-native
-march=armv8-a+flagm+lse+dotprod+rdma+crc+aes+sha3+fp16fml+rcpc+sb+ssbs+pauth

Is from the VMWare VM using gcc14.

I have successfully built nodejs with all of the listed extensions except for pauth. pauth crashes the build.

I used a /etc/portage/env/ file as described in the wiki https://wiki.gentoo.org/wiki/Knowledge_ ... er_package to isolate nodejs from the global =native in make.conf.

Code: Select all

COMMON_FLAGS="-O2 -pipe -march=armv8-a+flagm+lse+dotprod+rdma+crc+aes+sha3+fp16fml+rcpc+sb+ssbs"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"

pauth was the last of the 12 that I tried. Yes, they all needed to be tried, but, it took a while.

My intention is to leave =native global in make.conf and isolate the non-building packages in their own per-package build environment. The low hanging fruit is just -march=armv8-a ,but, time allowing I will try to identify the offending cpu extensions for any additional packages that fail to build in this manner.

[flysideways]

ruby is also fixed by not using the pauth cpu extension.

Code: Select all

COMMON_FLAGS="-O2 -pipe -march=armv8-a+flagm+lse+dotprod+rdma+crc+aes+sha3+fp16fml+rcpc+sb+ssbs"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"