-
Notifications
You must be signed in to change notification settings - Fork 125
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
Having trouble getting b2sum to compile on OS X #25
Comments
This may be helpful: Creating static Mac OS X C build. Apparently, GCC does not support the configuration. The trick to searching for this is to quote the library: "os x" brew ld: library not found for "-lcrt0.o". Otherwise, engines like Google think "all problems without the word lcrt0.o". (My apologies for jumping in. The Mac port tools, like Macports and Brew, have caused me a fair amount of non-standard trouble over the years). |
Removing the |
Tried:
It would be great if the project would keep this issue open and modify the makefile so that it will remove those options when run on OS X if there are no major negatives to doing so. Something along the lines of what is shown in this post might do the trick. https://discussions.apple.com/thread/1945589?tstart=0 Thanks for the help. |
The tricks shown in the makefile require a portable make, like GNUmake or Dmake. I believe BLAKE2 uses Posix's make, which is anemic. Folks use often GNUmake or Dmake because Posix make is so anemic. |
cc: @Scarletts |
5f2f566 disables |
Thanks, Perhaps this could be documented in a README.md in the b2sum dir for others? Unless you are very familiar with the nuances of the makefile most won't figure this out on their own... |
cb0506c adds a small README that explains the available build options. |
Thanks @sneves I think that tidies up this issue pretty well. Thanks for the help. Closing. |
I cannot get b2sum to compile on OS X (10.11.5 El Capitan). If I use the OS X command line compile tools installed with Xcode I see:
If I try to use homebrew installed
gcc
I get:Is this a bug, or am I doing it wrong?
The text was updated successfully, but these errors were encountered: