This message was deleted.
# configuration-cache
s
This message was deleted.
c
Not seeing that command (
sysctl -n hw.physicalcpu
) in the Gradle source - do we know where it comes from (stack trace)?
did find one occurrence in resolved asciidoctor JAR, a Ruby gem.
r
Its definitely part of the java tool chain support. likely part of gradle/native-platform
c
hmmm. have the latest Gradle source checked out (includes subprojects/native)- nothing is using
hw.physicalcpu
, nor are there suspect calls to
sysctl
. That specific sysctl command gets the processor count (not clear why that would be needed for toolchain resolution). Is there a stacktrace or some other indicator of where to look next?
the separate GitHub repo for native-platform also doesn’t reference hw.physicalcpu.
Is that call perhaps from here?
r
wow @Chris Lee. thanks a lot for going the extra mile and doing my work 😂 sorry for the noice for now. Not sure how this now shows up and havn't been an issue before
👍 1