libdatadog 0.7.0.1.0 → 0.7.0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/libdatadog/version.rb +1 -1
- data/lib/libdatadog.rb +17 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: ce4481b420b45c3ec9c3e9827e78e10c287ea88acf9c13bef324997c3bac46bb
|
|
4
|
+
data.tar.gz: 7c0d0c724f6012530fb828be921ca821a613afc83b367255f58c7723041f5777
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6aeed31b6d19055c3b6d1e6a479880c4011f034e20db0b4a1304ccc9cb3ff79d4ee0b89e95376fa02494daaa959569d6ba5f4445a59ef11977f487bb95755be8
|
|
7
|
+
data.tar.gz: ffc12e40228e7aed98cf9ed54f6c1c535827ab66ff431291020a8b6fe32f4264cd9d03b126046c9bd813eea9ee25127ebdd6942eadfbba502dc7d0b223b61042
|
data/lib/libdatadog/version.rb
CHANGED
|
@@ -5,7 +5,7 @@ module Libdatadog
|
|
|
5
5
|
LIB_VERSION = "0.7.0"
|
|
6
6
|
|
|
7
7
|
GEM_MAJOR_VERSION = "1"
|
|
8
|
-
GEM_MINOR_VERSION = "
|
|
8
|
+
GEM_MINOR_VERSION = "1"
|
|
9
9
|
GEM_PRERELEASE_VERSION = "" # remember to include dot prefix, if needed!
|
|
10
10
|
private_constant :GEM_MAJOR_VERSION, :GEM_MINOR_VERSION, :GEM_PRERELEASE_VERSION
|
|
11
11
|
|
data/lib/libdatadog.rb
CHANGED
|
@@ -11,6 +11,23 @@ module Libdatadog
|
|
|
11
11
|
def self.pkgconfig_folder(pkgconfig_file_name = "ddprof_ffi_with_rpath.pc")
|
|
12
12
|
current_platform = Gem::Platform.local.to_s
|
|
13
13
|
|
|
14
|
+
if RbConfig::CONFIG["arch"].include?("-musl") && !current_platform.include?("-musl")
|
|
15
|
+
# Fix/workaround for https://github.com/DataDog/dd-trace-rb/issues/2222
|
|
16
|
+
#
|
|
17
|
+
# Old versions of rubygems (for instance 3.0.3) don't properly detect alternative libc implementations on Linux;
|
|
18
|
+
# in particular for our case, they don't detect musl. (For reference, Rubies older than 2.7 may have shipped with
|
|
19
|
+
# an affected version of rubygems).
|
|
20
|
+
# In such cases, we fall back to use RbConfig::CONFIG['arch'] instead.
|
|
21
|
+
#
|
|
22
|
+
# Why not use RbConfig::CONFIG['arch'] always? Because Gem::Platform.local.to_s does some normalization we want
|
|
23
|
+
# in other situations -- for instance, it turns `x86_64-linux-gnu` to `x86_64-linux`. So for now we only add this
|
|
24
|
+
# workaround in a specific situation where we actually know it is wrong.
|
|
25
|
+
#
|
|
26
|
+
# See also https://github.com/rubygems/rubygems/pull/2922 and https://github.com/rubygems/rubygems/pull/4082
|
|
27
|
+
|
|
28
|
+
current_platform = RbConfig::CONFIG["arch"]
|
|
29
|
+
end
|
|
30
|
+
|
|
14
31
|
return unless available_binaries.include?(current_platform)
|
|
15
32
|
|
|
16
33
|
pkgconfig_file = Dir.glob("#{vendor_directory}/#{current_platform}/**/#{pkgconfig_file_name}").first
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: libdatadog
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.7.0.1.
|
|
4
|
+
version: 0.7.0.1.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Datadog, Inc.
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2022-
|
|
11
|
+
date: 2022-08-19 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
13
|
description: libdatadog is a Rust-based utility library for Datadog's ddtrace gem.
|
|
14
14
|
email:
|