vchepkov
04/17/2024, 9:15 PMYury Bushmelev
04/17/2024, 9:15 PMYury Bushmelev
04/17/2024, 9:16 PMbastelfreak
04/17/2024, 9:16 PMvchepkov
04/17/2024, 9:16 PMvchepkov
04/17/2024, 9:16 PMbastelfreak
04/17/2024, 9:16 PMvchepkov
04/17/2024, 9:18 PMvchepkov
04/17/2024, 9:18 PMvchepkov
04/17/2024, 9:19 PMvchepkov
04/17/2024, 9:19 PMbastelfreak
04/17/2024, 9:20 PMbastelfreak
04/17/2024, 9:21 PMvchepkov
04/17/2024, 9:21 PMbastelfreak
04/17/2024, 9:21 PMbastelfreak
04/17/2024, 9:21 PMvchepkov
04/17/2024, 9:22 PMCas Donoghue
04/17/2024, 9:22 PMCas Donoghue
04/17/2024, 9:23 PMvchepkov
04/17/2024, 9:23 PMbastelfreak
04/17/2024, 9:26 PMcsharpsteen
04/18/2024, 1:14 AMuname -m
, so getting x86_64
back means that is what macOS uname
returns in a Rosetta execution context:
$ uname -om
Darwin arm64
$ file /opt/puppetlabs/bolt/bin/ruby
/opt/puppetlabs/bolt/bin/ruby: Mach-O 64-bit executable x86_64
$ /opt/puppetlabs/bolt/bin/ruby -e 'puts %x{uname -om}'
Darwin x86_64
csharpsteen
04/18/2024, 1:16 AMuname
being a fat binary that contains implementations for both architectures:
$ file /usr/bin/uname
/usr/bin/uname: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
/usr/bin/uname (for architecture x86_64): Mach-O 64-bit executable x86_64
/usr/bin/uname (for architecture arm64e): Mach-O 64-bit executable arm64e
csharpsteen
04/18/2024, 1:21 AMx86_64
build of Bolt works amazingly well under Rosetta emulation. But, there are enough edge cases like this that a native build should get done eventually.ralfbosz
04/18/2024, 7:23 AMYury Bushmelev
04/18/2024, 8:28 AMepp()
function to work in a plan at all? I see Could not find template
error. My template is in templates/test.epp
file π€vchepkov
04/18/2024, 7:58 PM$ /opt/puppetlabs/bolt/bin/facter os.hardware
arm64
vchepkov
04/18/2024, 7:59 PM/opt/homebrew/bin/uname -> ../Cellar/coreutils/9.5/libexec/gnubin/uname
bastelfreak
04/18/2024, 8:03 PMbastelfreak
04/18/2024, 8:03 PM