0.8.2 fails to compile with rustc 1.48.0 due to unknown codegen option

[matthiasbeyer]

   Compiling env_logger v0.8.2                                                                                                                                                                                     
error: unknown codegen option: `embed-bitcode`                                                                                                                                                                     
error: could not compile `env_logger`

$ rustc --version
rustc 1.48.0 (7eac88abb 2020-11-16)

$ cargo --version
cargo 1.48.0 (65cbdd2dc 2020-10-14)

[matthiasbeyer]

Maybe some more information: I do not crosscompile anything. I compile a crate I developed on another system on a centos7 machine. I did a cargo clean run before retrying cargo build but it did not help, same error.

[matthiasbeyer]

Also, I just cloned this repository and it builds fine. But not if I have env_logger as a dependency. Not sure what is happening here...

[jplatte]

env_logger doesn't have a build script or anything else that I can see that could cause this. The string bitcode doesn't appear anywhere inside this repository. I would recommend you ask for help about this on users.rust-lang.org, Discord, reddit or some other place for general help and advice about Rust.

[matthiasbeyer]

Thanks for the fast reply. Apparently the compiler fails to understand an argument it gets ... don't know why tho.
Anyways, I'll report to users.rust-lang.org! Thank!

[BafDyce]

Hey @matthiasbeyer

Where you able to solve this issue? I am also hitting this error message, whenever I try to compile anything that has env_logger in its dependencies..

[matthiasbeyer]

Actually I'm not sure what solved that issue for me, sorry. Make sure to use an up-to-date version of the compiler and also make sure you don't mess up different versions in one installation. Happened to me before and is most certainly not the way to go! 😆

[sunshowers]

I'm hitting the same issue in a Docker build but with some more interesting output (we have a somewhat custom setup which bypasses the rustup wrapper to cargo but not rustc):

   Compiling env_logger v0.8.2
info: syncing channel updates for '1.41.0-x86_64-unknown-linux-gnu'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: using up to 500.0 MiB of RAM to unpack components
info: installing component 'clippy'
info: installing component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
info: installing component 'rustfmt'
error: unknown codegen option: `embed-bitcode`

error: could not compile `env_logger`

1.41.0 matches the rust-toolchain checked into env_logger, I suspect excluding this file from the crates.io release will fix it.

[sunshowers]

Yes, assuming you have a stable version of the Rust toolchain installed, this command reproduces the issue:

eval $(rustup which --toolchain stable cargo) build

Honestly this is almost certainly an upstream bug in Cargo -- but excluding rust-toolchain from the release on crates.io should work around it.

[jplatte]

Removing the rust-toolchain from the crates.io release should be easy enough and I don't see a reason not to do that 👍🏼

[jplatte]

Done in eed1651. I'll try to do a release in the coming days, feel free to ping me if I still haven't gotten to it next week.

[sunshowers]

@jplatte been a week so gentle ping, thanks! :)