rsnext/packages
Benjamin Woodruff f9ad49fc6f
test(turbopack): Add -Wl,--warn-unresolved-symbols to next-swc-napi on Linux (#64049)
I'm not sure why this issue is impacting me and seemingly not others,
but on Debian 12 with the default linker options (gcc with ld) I get the
following compilation error regarding unresolved symbols:

https://gist.github.com/bgw/92da94f46b0994514a144b8938aa2f6c

This flag downgrades that linker error to a warning (which cargo hides).

I've checked that this flag is supported by ld, gold, lld, and mold.
I've also tried building with mold in addition to ld. I'm restricting
the option to linux to avoid potentially breaking other platforms.

Tested by running:

```
cargo test -p next-swc-napi
```

Which now gives:

```
running 2 tests
test transform::test_deserialize_transform_regenerator ... ok
test transform::test_deser ... ok
```
2024-04-08 10:49:24 -07:00
..
create-next-app v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
eslint-config-next v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
eslint-plugin-next v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
font v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next Fix hydration error higlight when tag matched multi times (#64133) 2024-04-08 19:12:03 +02:00
next-bundle-analyzer v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-codemod v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-env v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-mdx v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-plugin-storybook v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-polyfill-module v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-polyfill-nomodule v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
next-swc test(turbopack): Add -Wl,--warn-unresolved-symbols to next-swc-napi on Linux (#64049) 2024-04-08 10:49:24 -07:00
react-refresh-utils v14.2.0-canary.62 2024-04-07 23:22:18 +00:00
third-parties v14.2.0-canary.62 2024-04-07 23:22:18 +00:00