-
Notifications
You must be signed in to change notification settings - Fork 849
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
Build: Make fails with the error "invalid for movq" and the warning "implicit conversion shortens 64-bit value". Workaround: Use clang instead of llvm-gcc. #1367
Comments
Hi @dgdy9hvz, Could you type echo $CC in a terminal where you have not exported CC=clang. Then could you tell us the version of that compiler (For example gcc -v if $CC is default set to gcc). Also is your Mac a 64-bit or 32-bit arch? Have you replaced the default gcc (which on a Mac usually just uses clang anyway)? It seems odd that using CC=clang on a Mac would change much unless using an alternate gcc. For example on my Mac I see:
Thus my request to see which version and which toolchain is being used by default. Thanks!
|
Also as a note, the reason I asked you to A: has $CC been set to something already and if so what and what version Thanks!
|
By default, the environment variable CC is empty, as Newer versions of Xcode come with only clang; hence, gcc invokes clang, as you point out. However, older versions of Xcode came with both llvm-gcc and clang. On the filesystem, /usr/bin/gcc was a symlink to llvm-gcc, and /usr/bin/cc was a symlink to clang. gcc did not invoke clang, as |
This should be resolved in recent updates to autoconf system. Let us know if the issue recurs. K |
I have found that
llvm-gcc
on Mac OS X fails to compile wolfssl-3.13.0. If gcc is a symlink to llvm-gcc, then, by adding the lineexport CC=clang
before./configure
,clang
must be forced to be used.I did this
The current directory is "wolfssl-3.13.0", to which "wolfssl-3.13.0.zip" expanded.
I expected the following
The "make" completes the compilation and link successfully.
what happened
The "make" terminates with errors. The following is the log that "make" printed. I replaced some paths with "[omitted]" in the log for security and privacy reasons. According to the "config.log",
CC='gcc'
.workaround
This problem can be avoided by adding the line
export CC=clang
before./configure
. Then, themake
successfully completes.environment
wolfssl-3.13.0
Mac OS X
The text was updated successfully, but these errors were encountered: