"next build" fails in environments with glibc < 2.18

[nana4gonta]

Run next info (available from version 12.0.8 and up)

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Sat Jul 3 21:51:47 UTC 2021
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 12.0.10-canary.2
      react: 17.0.2
      react-dom: 17.0.2

What version of Next.js are you using?

12.0.10

What version of Node.js are you using?

16.13.2

What browser are you using?

none

What operating system are you using?

Linux (Docker image based on CentOS 7)

How are you deploying your application?

Other

Describe the Bug

When I run next build, I get the error "/lib64/libc.so.6: version `GLIBC_2.18' not found" and cannot build.
It seems to have been fixed in swc (swc-project/swc#3314), so I would like to see it taken into the @next/swc package if possible.

$ # yarn run build
yarn run v1.22.17
$ next build
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

info  - Checking validity of types  
info  - Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /src/app/node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node)
info  - Attempted to load @next/swc-linux-x64-gnux32, but it was not installed
info  - Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory
error - Failed to load SWC binary for linux/x64, see more info here: https://nextjs.org/docs/messages/failed-loading-swc
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)

$ yum list installed | grep glibc
glibc.x86_64                            2.17-325.el7_9               @updates   
glibc-common.x86_64                     2.17-325.el7_9               @updates   
glibc-devel.x86_64                      2.17-325.el7_9               @updates   
glibc-headers.x86_64                    2.17-325.el7_9               @updates

Expected Behavior

Execution of next build succeeds even if GLIBC < 2.18.

To Reproduce

Run next build on CentOS 7 Docker image

in host OS

$ docker pull centos:7
$ docker run --rm -it centos:7 /bin/bash

in docker

# yum install gcc
# yum update
# curl -fsSL https://rpm.nodesource.com/setup_16.x | bash -
# yum install -y nodejs
# npx create-next-app@latest --typescript
# npm run build

[balazsorban44]

Thanks, I could reproduce it even on v12.0.11-canary.11.

[markerikson]

Yep, seeing the same issue.

I had actually run into this earlier on our project when I switched from babel-jest to @swc-node/jest. I worked around this by using the musl-libc build of SWC instead, but that actually required doing a custom build of libc.musl-x86_64.so.1 on a RHEL7 machine, committing it to our repo, and then setting LD_LIBRARY_PATH="./path/to/musl-libc/" in CI.

Not sure why that isn't working here. I can see Next trying to load the musl-libc build, but failing to find that shared lib:

info  - Checking validity of types...
info  - Creating an optimized production build...

info  - Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by $OUR_PROJECT/node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node)

info  - Attempted to load @next/swc-linux-x64-gnux32, but it was not installed

info  - Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory

I'll keep poking at this, but I'm wondering if maybe LD_LIBRARY_PATH isn't getting passed through to the process that is loading the binaries?

Overall, it looks like this would be fixed if Next could pull over those latest SWC build changes. Can we get that applied soon?

[Brooooooklyn]

It could be fixed with --zig cross toolchains with NAPI-RS v2: swc-project/swc#3314

I'll fix it after #34355 merge.

[markerikson]

@Brooooooklyn : Thank you! Just for reference so I can plan on my side, any idea roughly how long this might take for the fix to be available in a (pre-)release? (a day, a week, a month, ...?)

[Brooooooklyn]

It may take 1-2 days

[markerikson]

Tried updating our Next 12 upgrade branch to 12.1.1-canary.1, and confirmed that it now builds successfully on our RHEL7 Jenkins agent.

Thank you!

[nana4gonta]

Thank you.
I also tried it on my environment by upgrading to 12.1.1-canary.1 and the build was successful.