Stream: general

Topic: rustc --print native-static-libs


Luca Barbato (May 23 2019 at 12:52, on Zulip):

what's the sanest way to not litter the directory with libnull.a when just asking rustc the static-libs ?

RalfJ (May 23 2019 at 14:18, on Zulip):

looks like a bug? rustc --print sysroot does not create a libnull.a

Eric Huss (May 23 2019 at 15:45, on Zulip):

Oh, I just recently documented that flag, I think that's intentional that it will perform a full compilation. Historically it was always displayed during compilation, and it was changed to only display the link list with the --print flag. I think it is geared towards "you just built a staticlib, here's how you can link it". And some people didn't like that it always printed it, so it was changed to a flag. Also, presumably, the answer isn't known until translation phase. It's definitely an odd flag, as it's the only one that doesn't stop compilation.

Luca Barbato (May 26 2019 at 10:40, on Zulip):

If is this behavior is set and intentional I can try to workaround it

Luca Barbato (May 26 2019 at 10:40, on Zulip):

Otherwise I'd change it

Luca Barbato (May 26 2019 at 10:40, on Zulip):

since it is really brittle

Last update: Nov 20 2019 at 13:00UTC