LLVM ERROR: Program used external function '...' which could not be resolved!

KIMURA Masaru hiyuh.root@gmail.com
Mon Feb 20 17:53:00 GMT 2012


Hi,

2012/2/20 KIMURA Masaru <hiyuh.root@gmail.com>:
> And more Google'ing, I found this post on LLVMdev ML:
>
>  http://lists.cs.uiuc.edu/pipermail/llvmdev/2005-June/004364.html
>
>  > 2. The LLI test failures occur because the dlsym function on cygwin can
>  > only find symbols in a loaded DLL. If the symbol is in the .EXE file
>  > then the symbol doesn't get found. Since LLI links in things like
>  > printf, strcat, and some other fundamental functions, they don't get
>  > found on Cygwin. A similar thing happens on MacOS but for a much
>  > smaller set of files for which we hand code a workaround. The set
>  > of functions on Cygwin is basically a large fraction of glibc, too
>  > much to do by hand.
>
> But this is back in 2005, I don't know this is still correct in 2012,
> LLVM-3.0 and Cygwin-1.7.

I've tried to build nvc w/ stub DLL, the errors are gone and it works fine.
I guess this issue still stands. (maybe upstream WONTFIX?)

anyway, thank you to marco for trying help.
and sorry for noise again.

Peace,

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list