-
Notifications
You must be signed in to change notification settings - Fork 659
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
Compiling from repository in Mac OS X error #13
Comments
It looks like "indent" does not like the "-kr" option. "indent" is a program that reformats C code (we use it to pretty-print codelets); "-kr" specifies that we want the style from the K&R C book (the only true style). I am not familiar with OSX---perhaps it has a different version of indent. Can you try editing support/Makefile.codelets, find the INDENT= line, and replace it with INDENT = cat Even better, please tell us how the OSX indent should be invoked so that we can patch FFTW. Thanks, |
OSX has the BSD version of |
Seems that instead of the -kr option one should use(for BSD indent):
Readed from here: http://stackoverflow.com/questions/1352104/how-do-i-tell-usr-bin-indent-on-mac-os-x-10-5-to-format-my-c-code-kr-style However does not work, I end up installing gnu-indent and changing the line in support/Makefile.codelets to:
Then I get the error:
|
Did the codelet builds work? I assume you have |
Yes the codelet builds and ocaml is installed,
|
…ndent. BSD 'indent' in e.g. MacOSX doesn't support -kr, which is the default style in FFTW3. Fallback to 'indent' with no option for non-GNU 'indent', or 'cat' if 'indent' is not available. This should fix GitHub issue #13.
The 'indent' issue should be fixed now. As for the undefined symbols, it's likely the 'indent' failure caused empty codelet files to be generated. Remove them and try to rebuild (i.e. "find fftw3/ -type f -name '*.c' -size 0 -exec rm -f {} ;"). |
2> problem.c |
In OSX 10.9.2 with all the dependencies: autoconf, autolib, ocaml, ...
Downloading the repo and running:
Produces an error:
The text was updated successfully, but these errors were encountered: