compilation errors during build

[cml54]

I downloaded zpar wrapper and ran ‘make’ in order to build zpar and zpar wrapper.
But, I got the following error:

In file included from ./src/include/hash.h:25:
./src/include/hash_stream.h:18:11: error: call to function 'operator>>' that is neither
      visible in the template definition nor found by argument-dependent lookup
      iss >> table[key] ;
          ^
./src/common/tagger/implementations/collins/tagger.h:118:9: note: in instantiation of
      function template specialization 'operator>><CWord, english::CTag>' requested here
      i >> (*m_TopTags);
        ^
./src/english/tags.h:29:23: note: 'operator>>' should be declared prior to the call site
      or in namespace 'english'
inline std::istream & operator >> (std::istream &is, english::CTag &tag) {
                      ^
1 error generated.
make[1]: *** [obj/english.postagger.o] Error 1
make: *** [python-zpar] Error 2

Can you advise me how to resolve the error?

[desilinguist]

I just cloned and built on both OS X and Linux and it works fine for me. Can you tell where you are building this? You may need to install gcc using macports if you are doing it on your mac.

[cml54]

I tried to build it on OS X. I installed gcc using HomeBrew:

gcc --version

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1

Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)

Target: x86_64-apple-darwin13.1.0

Thread model: posix

Do I need to update gcc?

On Tue, Sep 16, 2014 at 10:50 AM, Nitin Madnani notifications@github.com
wrote:

I just cloned and built on both OS X and Linux and it works fine for me.
Can you tell where you are building this? You may need to install gcc using
macports if you are doing it on your mac.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[desilinguist]

Looks like it's still using the apple default gcc instead of the homebrew one. Is your path set correctly? I don't use homebrew so I can't be sure. I know it works with macports.

[cml54]

You're right. After my reply, I found that I didn't install gcc. So, I
installed gcc using brew. it took a while in installing it :-( And, the
error was gone.

Thanks,
Chong Min

On Tue, Sep 16, 2014 at 4:29 PM, Nitin Madnani notifications@github.com
wrote:

Looks like it's still using the apple default gcc instead of the homebrew
one. Is your path set correctly? I don't use homebrew so I can't be sure. I
know it works with macports.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[bdewilde]

Hi, I'm getting the same error as the original poster. I do have Homebrew's gcc-4.9 installed and have tried to force its use in several ways: I've aliased gcc=gcc-4.9 in my bash profile; I've specified it in the setup command as CC=gcc-4.9 python setup.py install; I've added the line os.environ["CC"] = "gcc-4.9" to setup.py, but the error is always the same. I don't know what else to try — any help would be much appreciated!

Thanks,
Burton

[desilinguist]

You might want to make sure that g++ also points to the g++ installed by Homebrew and not the one provided as part of clang. I think one of my colleagues had the same issue. Let me know if that still doesn't work.

[bdewilde]

Thanks for the quick response! I repeated my earlier attempts but replaced gcc-4.9 with g++-4.9 in all cases. Unfortunately, the error was unchanged. What else might I try?

[desilinguist]

Can you please post the output of which gcc, which g++ and g++ --version here?

[bdewilde]

Sure:

python-zpar-master$ which gcc
gcc: aliased to gcc-4.9
python-zpar-master$ gcc --version
gcc-4.9 (Homebrew gcc 4.9.1) 4.9.1
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

and

python-zpar-master$ which g++
g++: aliased to g++-4.9
python-zpar-master$ g++ --version
g++-4.9 (Homebrew gcc 4.9.1) 4.9.1
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[desilinguist]

Hmm, that's really strange. What about modifying the CXX variable in src/Makefile to have the absolute path to the Homebrew g++?

[bdewilde]

Thanks for all the suggestions! Modifying src/Makefile to have CXX = /usr/local/Cellar/gcc/4.9.1/bin/g++-4.9 seems to have worked! Although it's odd that the original CXX=g++ did not. Can't wait to get up and running with zpar.

[desilinguist]

Glad that worked. Not an ideal solution though.

[desilinguist]

Okay, I think I figured out a better way to override the CXX variable. What you can do is to run CXX=<path to homebrew g++> make -e instead of make. Would you mind running testing if this works in a fresh clone of the repository? I'd appreciate it.