Installing on MAC OS X

[atishsawant]

I’m using MAC OSX and the command:

CXX=/usr/bin/gcc make –e

Doesn’t work when I’m in the unzipped directory? It seems like it fails on the wget command for the underlying zpar from github. Actual output:

make: wget: No such file or directory

**Actually just solved this part.

Still results in this error eventually though:

error: call to function 'operator>>' that is
neither visible in the template definition nor found by argument-dependent
lookup

Same one that I get in the individual zpar directory when trying to install it independently.

So I downloaded the individual zpar, and tried to install that separately but that one leads to errors that I believe are related to clang. Using the same CXX command within that file also didn’t work.

[desilinguist]

Are you sure you have wget installed and in your path?

…

On Wed, Feb 7, 2018 at 11:28 AM atishsawant ***@***.***> wrote: I’m using MAC OSX and the command: CXX=/usr/bin/gcc make –e Doesn’t work when I’m in the unzipped directory? It seems like it fails on the wget command for the underlying zpar from github. Actual output: make: wget: No such file or directory So I downloaded the individual zpar, and tried to install that separately but that one leads to errors that I believe are related to clang. Using the same CXX command within that file also didn’t work. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJ3kM7KJqP5OZ8koVQ3dVmCFWjs0W8Hks5tSc80gaJpZM4R8_wM> .

[atishsawant]

That was my earlier mistake. I fixed that. THe call to function error still persists however.

[desilinguist]

Did you read the warning in the README about how clang will not work and you need to install gcc via either macports or homebrew?

[atishsawant]

Yep, I used the CXX command as noted to point to the gcc compiler instead to run. But that still persisted.

[desilinguist]

Can you tell me what `/usr/bin/gcc --version` prints out?

…

On Wed, Feb 7, 2018 at 14:34 atishsawant ***@***.***> wrote: Yep, I used the CXX command as noted to point to the gcc compiler instead to run. But that still persisted. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJ3kPuOty0UWAtVbaDfNuAt8vMRWc4nks5tSfqtgaJpZM4R8_wM> .

[atishsawant]

Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.0.0 (clang-900.0.39.2)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

is the result.

[desilinguist]

This is why I asked you earlier if you followed the instructions properly. As the README clearly says, the default macOS compiler (clang) will not work. Please install gcc via MacPorts or home brew and use that.

…

On Wed, Feb 7, 2018 at 3:12 PM atishsawant ***@***.***> wrote: Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 9.0.0 (clang-900.0.39.2) Target: x86_64-apple-darwin16.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin is the result. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJ3kLfnmwdqOxqhgHxr3j_xK0hAOkKiks5tSgOngaJpZM4R8_wM> .

[atishsawant]

GCC is already installed. I thought by pointing it to /usr/bin/gcc it would fix the problem?

brew install gcc results in "Warning: gcc 7.3.0 is already installed"

[atishsawant]

Solved the problem. On newer MAC OS X's brew installing gcc, doesn't make the gcc in /usr/bin point to the gcc compiler and it will still be clang. Have to go to where brew installed gcc, and pick out a gcc version from there to compile with.
It still kicked out an error when compiling from the correct file, but in the second run it worked just fine.