libdatadog 0.7.0.1.0-aarch64-linux → 0.8.0.1.0-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 18cd650f8f6b37823d909b43ef3f15fb4de9ee739becff54005e13b3f3dd4973
-  data.tar.gz: da35267f0f5239ee74fc1a54bfae276dd3b6ed346323a12de0d7e57c32ad42b4
+  metadata.gz: 0e5d6a857bd4783854bff714f07b8636ef08139361df2777a95c2ebc5a084844
+  data.tar.gz: 90fad4e92e2b6ee6930762e2d3f8aa8979b2198fe26bc41ebe10db48fc814f38
 SHA512:
-  metadata.gz: e008bbb50de309054606f8bbd456d9276b24be95ea0f4ffb0485e11303b788820c73c6186d7144c2e83ba7d2c87c595c9eccc7d5606c32c74cc2c8a569f0af0e
-  data.tar.gz: 571ac42fdef04726e9699ebb99c58d81c9926f42a30e246802113df8c89b22b5b1f7732484f8866ba77a011f9ff8500efbfef97988f9f71f77db6bbdb37a99d8
+  metadata.gz: 550d7b9ed80dfb8fa9454e1bfeaf231de56575ded72159d3c775a108b1b035e7385915de50f986b4c31f5da05b761bb727e910ad98dd0634bf6a6e3249e97958
+  data.tar.gz: ad931129098f15e3c2b4845955d1f09e4cb13bb3e1a9fcbb7d9f4081d5ffe19947834f6b80ed78e376502d640e7c6ed4eb51d87ba76b72e3735b710a2ba382dc

data/lib/libdatadog/version.rb

@@ -2,7 +2,7 @@
 
 module Libdatadog
   # Current libdatadog version
-  LIB_VERSION = "0.7.0"
+  LIB_VERSION = "0.8.0"
 
   GEM_MAJOR_VERSION = "1"
   GEM_MINOR_VERSION = "0"

data/lib/libdatadog.rb

@@ -8,9 +8,26 @@ module Libdatadog
     File.directory?(vendor_directory) ? (Dir.entries(vendor_directory) - [".", ".."]) : []
   end
 
-  def self.pkgconfig_folder(pkgconfig_file_name = "ddprof_ffi_with_rpath.pc")
+  def self.pkgconfig_folder(pkgconfig_file_name = "datadog_profiling_with_rpath.pc")
     current_platform = Gem::Platform.local.to_s
 
+    if RbConfig::CONFIG["arch"].include?("-musl") && !current_platform.include?("-musl")
+      # Fix/workaround for https://github.com/DataDog/dd-trace-rb/issues/2222
+      #
+      # Old versions of rubygems (for instance 3.0.3) don't properly detect alternative libc implementations on Linux;
+      # in particular for our case, they don't detect musl. (For reference, Rubies older than 2.7 may have shipped with
+      # an affected version of rubygems).
+      # In such cases, we fall back to use RbConfig::CONFIG['arch'] instead.
+      #
+      # Why not use RbConfig::CONFIG['arch'] always? Because Gem::Platform.local.to_s does some normalization we want
+      # in other situations -- for instance, it turns `x86_64-linux-gnu` to `x86_64-linux`. So for now we only add this
+      # workaround in a specific situation where we actually know it is wrong.
+      #
+      # See also https://github.com/rubygems/rubygems/pull/2922 and https://github.com/rubygems/rubygems/pull/4082
+
+      current_platform = RbConfig::CONFIG["arch"]
+    end
+
     return unless available_binaries.include?(current_platform)
 
     pkgconfig_file = Dir.glob("#{vendor_directory}/#{current_platform}/**/#{pkgconfig_file_name}").first