Fails to link -no-pie executable that depends on a proc macro

[dtolnay]

The following script reproduces the issue. We create a library mac which is a procedural macro (an empty one is sufficient) and a binary repro which depends on mac.

#!/bin/sh

cargo new mac
echo >>mac/Cargo.toml '
[lib]
proc-macro = true
'

cargo new repro --bin
echo >>repro/Cargo.toml '
mac = { path = "../mac" }
'

RUSTFLAGS='-C link-args=-no-pie' cargo run --manifest-path repro/Cargo.toml

The link step fails with:

error: linking with `cc` failed: exit code: 1
  = note: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crt1.o: In function `_start':
          (.text+0x20): undefined reference to `main'
          collect2: error: ld returned 1 exit status

Originally reported in serde-rs/serde#1166. @fintelia

[alexcrichton]

This is unfortunately sort of expected, RUSTFLAGS is quite dangerous for precisely the reason, that it can't be targeted to particular crates causing things like link flags to go awry.

I'm not really sure if this can be fixed per se, but this is likely related to a new feature like rust-lang/rust#48683

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[AregevDev]

It is still relevant by now, I am facing the same issue

[AregevDev]

Any news regaurding that?

[Yuri6037]

That's a huge issue: currently this prevents the creation of double-click to run type softwares