netty: [Question] DNS native resolver for Apple Silicon M1 still not working?
DNS native resolver for Apple Silicon M1 still doesn’t work for me.
Same issue as mentioned here: https://github.com/netty/netty/issues/11020#issue-806940633
Netty version
netty-resolver-dns-native-macos-4.1.68.Final.jar
JVM version (e.g. java -version)
openjdk version “16.0.2” 2021-07-20 OpenJDK Runtime Environment Zulu16.32+15-CA (build 16.0.2+7) OpenJDK 64-Bit Server VM Zulu16.32+15-CA (build 16.0.2+7, mixed mode)
OS version (e.g. uname -a)
Darwin Larss-Air.fritz.box 21.1.0 Darwin Kernel Version 21.1.0: Thu Aug 19 02:54:44 PDT 2021; root:xnu-8019.40.29~26/RELEASE_ARM64_T8101 arm64
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 15 (6 by maintainers)
Commits related to this issue
- Add osx-x86_64 netty-resolver-dns-native-macos dependency (#3995) Motivation: Unable to load io.netty.resolver.dns.macos.MacOSDnsServerAddressStreamProvider on M1 MAC Same problem with netty's next ... — committed to line/armeria by woohhan 3 years ago
- fix: fix error ref: https://github.com/netty/netty/issues/11693 — committed to THE-BAETLES/chord-play-api-server by chanwooDev 2 years ago
Yeah, it should be
osx-aarch_64.I think the others are typos. The
osx-aarch_64classifier is the correct one.To Maven, the
classifiertag is an opaque string that is used to distinguish artefacts that were built from the same pom but differ in contents. So, no, it’s not automatic. The reason you don’t need to specify a classifier for many other libraries that carry native code, is that they include native binaries for all supported platforms in a single jar file.Why do we need to specify the
classifier, shouldn’t that be handled automatically?Resolved by adding io.netty:netty-all:4.1.68.Final.