xanewok / issue-copy-test Goto Github PK

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-rustc#1):

Sometimes we don't want to run it, currently the shim does it every time.

Originally created by @Xanewok (Xanewok/source-issue-test#2):

With body

Originally created by @ (rust-dev-tools/rls-rustc#10):

I tried to use this shim, but it didn't work. Maybe I'm doing it wrong? I built it and then tried to use the generated rustc shim as a drop-in replacement for rustc to build it again.

$ cargo +nightly build --release
$ mv target target.old
$ RUSTC_WRAPPER=target.old/release/rustc cargo +nightly build
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 101)
--- stderr
error: multiple input filenames provided

Also I get a different error if I run that last step without +nightly:

$ RUSTC_WRAPPER=target.old/release/rustc cargo build
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (signal: 6, SIGABRT: process abort signal)
--- stderr
dyld: Library not loaded: @rpath/librustc_driver-51f1276ab2f3d846.dylib
  Referenced from: /Users/kats/zspace/rls-rustc/target.old/release/rustc
  Reason: image not found

I get the same errors when trying to use the shim to build other rust crates (ones that build fine with release-version rust).

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-rustc#1):

Sometimes we don't want to run it, currently the shim does it every time.

Originally created by @dweinstein
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @dweinstein (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Author dweinstein
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (Xanewok/source-issue-test#2):

With body

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-rustc#10):

I tried to use this shim, but it didn't work. Maybe I'm doing it wrong? I built it and then tried to use the generated rustc shim as a drop-in replacement for rustc to build it again.

$ cargo +nightly build --release
$ mv target target.old
$ RUSTC_WRAPPER=target.old/release/rustc cargo +nightly build
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 101)
--- stderr
error: multiple input filenames provided

Also I get a different error if I run that last step without +nightly:

$ RUSTC_WRAPPER=target.old/release/rustc cargo build
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (signal: 6, SIGABRT: process abort signal)
--- stderr
dyld: Library not loaded: @rpath/librustc_driver-51f1276ab2f3d846.dylib
  Referenced from: /Users/kats/zspace/rls-rustc/target.old/release/rustc
  Reason: image not found

I get the same errors when trying to use the shim to build other rust crates (ones that build fine with release-version rust).

Originally created by @ (Xanewok/source-issue-test#1):

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Author
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @ (rust-dev-tools/rls-blacklist#4):

Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?

Originally created by @Xanewok (Xanewok/source-issue-test#1):

Originally created by @ (rust-dev-tools/rls-rustc#1):

Sometimes we don't want to run it, currently the shim does it every time.