-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x86_64 MSVC coretest::ptr::test_variadic_fnptr: "error LNK2019: unresolved external symbol" #36076
Comments
printf function is not a thing in MSVC. That test ought to be removed, because we test variadic functions in this test, including the function pointer. |
Why aren't the MSVC bots seeing the same error, then? |
Well existence of an actual function might depend on MSVC version, I guess. (e.g. the ulibc and the old libc implementation) Perhaps that’s the reason buildbots haven’t been failing?
I really meant to say that it is not guaranteed to be a function and may be a macro too (i.e. does not export a symbol to link to) |
@nagisa If we can detect whether we're using a new enough MSVC version, we can tell the Rust to tell the linker to link |
Why? Just use the test helper we have exactly for this issue. On Aug 29, 2016 7:06 AM, "Peter Atashian" notifications@github.com wrote:
|
@nagisa Well sure, that's probably easier and more reliable. |
Are the test helpers available to coretest? Because Edit: They are not. |
… r=brson Fix the test_variadic_ptr fn on printf-less sys Fixes rust-lang#36076
I get a linker error when building coretest as part of the
check
step, or more specificallycheck-crate-std
. The source of the problem is the testtest_variadic_fnptr
insrc/coretest/ptr.rs
, and the same error can be provoked by this self-contained program:Some notes:
clone
and subsequently eliminate all the code including the part taking the address ofprintf
, and then it compiles just fine.fabs
in place ofprintf
worked just fine.Meta
Reproduced with a rustup-provided nightly from August 21 and with the current bootstrap compiler (beta-2016-08-17).
The text was updated successfully, but these errors were encountered: