Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

🐛 Error compiling simple rust project: multiple input filenames provided

See original GitHub issue

🐛 bug report

🎛 Configuration (.babelrc, package.json, cli command)

package.json

{
  "name": "rust-wasm",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "MIT",
  "dependencies": {
    "parcel-bundler": "^1.5.1"
  }
}

Run parcel index.js

🤔 Expected Behavior

Should compile

😯 Current Behavior

Console output:

Server running at http://localhost:1234
🚨  /Users/rob/Development/testing/web/rust-wasm/ops.rs: Command failed: rustc +nightly --target wasm32-unknown-unknown -O --crate-type=cdylib /Users/rob/Development/testing/web/rust-wasm/ops.rs -o /Users/rob/Development/testing/web/rust-wasm/.cache/933d122f8546a30c5660c45821247fad.wasm
error: multiple input filenames provided

error: multiple input filenames provided


    at ChildProcess.exithandler (child_process.js:275:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)

🔦 Context

Just a simple test of Rust support

💻 Code Sample

index.js

import { add } from './ops.rs'

console.log(add(4, 6))

ops.rs

#[no_mangle]
pub fn add(a: i32, b: i32) -> i32 {
  return a + b
}

🌍 Your Environment

Software	Version(s)
Parcel	1.5.1
Node	v8.9.3
npm/Yarn	npm 5.5.1
Operating System	macOS 10.13.4 beta (17E139j)
Rust	nightly-x86_64-apple-darwin unchanged - rustc 1.25.0-nightly (90eb44a58 2018-01-29)

Issue Analytics

State:
Created 6 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

robjtedecommented, Feb 1, 2018

Okay, so it turns out that rustc installed via homebrew doesn’t respect the +nightly modifier. That coupled with rustup being used to install toolchains and such results in the case where the toolchains are installed to the ~/.cargo installation but parcel tries to use (rightly) the first occurence of rustc in the PATH; which in this case was the homebrew version.

TL;DR: uninstalled homebrew version. it works now.

0reactions

albizurescommented, Feb 1, 2018

ooh right, so but you could try, setting nightly as default and without the flag