libdatadog 0.7.0.1.0 → 2.0.0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 631455d7d62a0281435df76425bfee4091aa653f441cc75792d1a727fb4903a5
-  data.tar.gz: ce4639f1688a301e6afd8e0ecb19ebb8ac117bdd385411fa04c2b59f068416c7
+  metadata.gz: 76a7e136cd6cf9297e85c223ed571751dc6ede185a9ceeca70114171b933d650
+  data.tar.gz: '089d17eb9cc5fbbbd584aac4620a256e385b3bd3178d8670e25c4be3aba42394'
 SHA512:
-  metadata.gz: f5ddb3dde1776e01aa200473aa2fd189e7333c3187c1b7d009fae55986bd25195f47ca68c620b39d7cf01a46ae591eebda428738be353e15228eb2e48eefed4d
-  data.tar.gz: d1093cb12956e3dfffdabbf73f965087578313abac085e485cbb2759b4935c0d0ba8e8c96584038a11a6c38a5fca53c8569e8f16e02d2f909df808b7cadacc47
+  metadata.gz: df384301ed0a3974428d01c755e73e4d6dfffc2fe843f4e9b6570a5137dd9c36773be084db496832dec40f9c5bf8b542e876fe67005ab1acbaca1164bd368999
+  data.tar.gz: e529479f6f0e3d5e1f232f5fbf7a09aaa572eecc1de77025c36dee24adef45671345be50157f9b929860fa35c652ac9612e377c901ac86122aba63a492c713c9

data/lib/libdatadog/version.rb

@@ -2,7 +2,7 @@
 
 module Libdatadog
   # Current libdatadog version
-  LIB_VERSION = "0.7.0"
+  LIB_VERSION = "2.0.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