Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /lib64/libc.so.6: version `GLIBC_2.32' not found #54017

Closed
1 task done
styfle opened this issue Aug 14, 2023 · 2 comments
Closed
1 task done

Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /lib64/libc.so.6: version `GLIBC_2.32' not found #54017

styfle opened this issue Aug 14, 2023 · 2 comments
Assignees
@kwonoj @ijjk
Labels
linear: next Confirmed issue that is tracked by the Next.js team. locked SWC Related to minification/transpilation in Next.js.

Comments

@styfle
Copy link
Member

styfle commented Aug 14, 2023 •
edited
Loading

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:19 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.17.0
      npm: 9.6.7
      Yarn: 1.22.19
      pnpm: 8.3.1
    Relevant Packages:
      next: 13.4.15-canary.0
      eslint-config-next: 13.4.15-canary.0
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

SWC transpilation

Link to the code that reproduces this issue or a replay of the bug

vercel/vercel#10339

To Reproduce

vercel deploy

Describe the Bug

SWC Wasm is used when deploying to Vercel

- info Creating an optimized production build...
- info Downloading swc package @next/swc-wasm-nodejs...
- info Using wasm build of next-swc
- warn Attempted to load @next/swc-linux-x64-gnu, but an error occurred: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /vercel/path0/node_modules/@next/swc-linux-x64-gnu/next-swc.linux-x64-gnu.node)
- warn 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

Expected Behavior

Expected native dependency when deploying to Vercel

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

NEXT-1516
@styfle styfle added bug Issue was opened via the bug report template. kind: bug linear: next Confirmed issue that is tracked by the Next.js team. and removed bug Issue was opened via the bug report template. labels Aug 14, 2023
@github-actions github-actions bot added the SWC Related to minification/transpilation in Next.js. label Aug 14, 2023
@styfle styfle mentioned this issue Aug 14, 2023
Closed
@styfle
Copy link
Member Author

styfle commented Aug 15, 2023

Fixed in 13.4.16

@styfle styfle closed this as completed Aug 15, 2023
@kwonoj kwonoj mentioned this issue Aug 15, 2023
Merged
ijjk pushed a commit that referenced this issue Aug 15, 2023
@kwonoj @styfle
chore(ci): small notes for the build steps (#54073)
61e1858 
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

### What?

Leaving a small note to the build steps to avoid regressions like
#54017 later.


Closes WEB-1386

---------

Co-authored-by: Steven <steven@ceriously.com>
@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 2023
@styfle styfle linked a pull request Oct 18, 2023 that will close this issue
Revert "chore(next/image): remove deprecation of onLoadingComplete temporarily" #57024
Merged
@styfle styfle removed a link to a pull request Oct 18, 2023
Revert "chore(next/image): remove deprecation of onLoadingComplete temporarily" #57024
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kwonoj kwonoj

@ijjk ijjk

Labels
linear: next Confirmed issue that is tracked by the Next.js team. locked SWC Related to minification/transpilation in Next.js.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@styfle @kwonoj @ijjk