Improves the check for the libc presence (#5971)

**What's the problem this PR addresses?**

The libc detection can currently be really slow on Linux systems due to
deficiencies in the Node.js `getReport` implementation.

**How did you fix it?**

As a workaround, we now first check the `ldd` content.

**Checklist**
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

Author: arcanis

.yarn/versions/d6853e56.yml

@@ -0,0 +1,34 @@
+releases:
+  "@yarnpkg/cli": patch
+  "@yarnpkg/core": patch
+
+declined:
+  - "@yarnpkg/plugin-compat"
+  - "@yarnpkg/plugin-constraints"
+  - "@yarnpkg/plugin-dlx"
+  - "@yarnpkg/plugin-essentials"
+  - "@yarnpkg/plugin-exec"
+  - "@yarnpkg/plugin-file"
+  - "@yarnpkg/plugin-git"
+  - "@yarnpkg/plugin-github"
+  - "@yarnpkg/plugin-http"
+  - "@yarnpkg/plugin-init"
+  - "@yarnpkg/plugin-interactive-tools"
+  - "@yarnpkg/plugin-link"
+  - "@yarnpkg/plugin-nm"
+  - "@yarnpkg/plugin-npm"
+  - "@yarnpkg/plugin-npm-cli"
+  - "@yarnpkg/plugin-pack"
+  - "@yarnpkg/plugin-patch"
+  - "@yarnpkg/plugin-pnp"
+  - "@yarnpkg/plugin-pnpm"
+  - "@yarnpkg/plugin-stage"
+  - "@yarnpkg/plugin-typescript"
+  - "@yarnpkg/plugin-version"
+  - "@yarnpkg/plugin-workspace-tools"
+  - "@yarnpkg/builder"
+  - "@yarnpkg/doctor"
+  - "@yarnpkg/extensions"
+  - "@yarnpkg/nm"
+  - "@yarnpkg/pnpify"
+  - "@yarnpkg/sdks"

packages/yarnpkg-core/sources/nodeUtils.ts

@@ -1,8 +1,8 @@
-import {ppath}        from '@yarnpkg/fslib';
-import os             from 'os';
+import {PortablePath, ppath, xfs} from '@yarnpkg/fslib';
+import os                         from 'os';
 
-import * as execUtils from './execUtils';
-import * as miscUtils from './miscUtils';
+import * as execUtils             from './execUtils';
+import * as miscUtils             from './miscUtils';
 
 export const major = Number(process.versions.node.split(`.`)[0]);
 
@@ -23,12 +23,29 @@ export const openUrl = typeof openUrlBinary !== `undefined`
   }
   : undefined;
 
+const LDD_PATH = `/usr/bin/ldd` as PortablePath;
+
 function getLibc() {
   // Darwin and Windows have their own standard libraries, and the getReport() call is costly.
   // It also seems that Node randomly crashes with no output under some circumstances when running a getReport() on Windows.
   if (process.platform === `darwin` || process.platform === `win32`)
     return null;
 
+  let header: Buffer | undefined;
+  try {
+    header = xfs.readFileSync(LDD_PATH);
+  } catch {}
+
+  // Since the getReport can be prohibitely expensive (it also queries DNS which, if misconfigured, can take a long time to timeout),
+  // we first check if the ldd binary is glibc or musl, and only then run the getReport() if we can't determine the libc variant.
+  if (typeof header !== `undefined`) {
+    if (header && header.includes(`GLIBC`))
+      return `glibc`;
+    if (header && header.includes(`musl`)) {
+      return `musl`;
+    }
+  }
+
   const report: any = process.report?.getReport() ?? {};
   const sharedObjects: Array<string> = report.sharedObjects ?? [];