Unrecognized processor during build

[magikid]

🐛 Bug description

When I run wasm-pack build, the build output has tons of lines saying 'core2' is not a recognized processor for this target (ignoring processor)

❯ wasm-pack build
[INFO]: 🎯  Checking for the Wasm target...
[INFO]: 🌀  Compiling to Wasm...
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
warning: function is never used: `set_panic_hook`
 --> src/utils.rs:1:8
  |
1 | pub fn set_panic_hook() {
  |        ^^^^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
'core2' is not a recognized processor for this target (ignoring processor)
    Finished release [optimized + debuginfo] target(s) in 0.06s
[INFO]: ⬇️  Installing wasm-bindgen...
[INFO]: Optimizing wasm binaries with `wasm-opt`...
[INFO]: Optional fields missing from Cargo.toml: 'description', 'repository', and 'license'. These are not necessary, but recommended
[INFO]: ✨   Done in 0.28s
[INFO]: 📦   Your wasm pkg is ready to publish at /Users/cjone0102/projects/personal/wasm-fibonacci/wasm-fib/pkg.

🤔 Expected Behavior

I expect to only see relevant log messages.

👟 Steps to reproduce

I've been seeing this issue since I used cargo-generate to create this package with the command cargo generate --git https://github.com/rustwasm/wasm-pack-template.git --name wasm-fib.

🌍 Your environment

Include the relevant details of your environment. wasm-pack version: wasm-pack 0.9.1 rustc version: rustc 1.42.0 (b8cedc004 2020-03-09)

I'm on a Macbook running Catalina. Here are some other tidbits that might be useful.

❯ uname -a
Darwin C02VJ026HTD8 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
❯ sysctl -n machdep.cpu.brand_string
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz

I've also uploaded my Cargo.toml and Cargo.lock files here: https://gist.github.com/magikid/74e0bb7cdff02ad93506bb393bf1bf03

[Turakar]

I found this to happen if I set target-cpu=native in my cargo config. Maybe wasm-pack could overwrite this with the WASM target?

[FL33TW00D]

I found this to happen if I set target-cpu=native in my cargo config. Maybe wasm-pack could overwrite this with the WASM target?

Removing this spared me the warning message.