This is kind of frustrating … so, the recommended way is to use apples clang and to built boost from source, is that correct? I thought I could pull gcc and boost out of macpots (as I used to do) and they would understand each other, but this does not seem to work. Why not?
Well, thanks anyway. I will try with a fresh boost built ... Jörg > On 01 Sep 2015, at 15:21, Hieu Hoang <[email protected]> wrote: > > My advice on osx is don't install GCC. Clang is the ordained compiler now, > you'll be fighting apple every step of the way. Don't think different! > > Hieu Hoang > Sent while bumping into things > > On 31 Aug 2015 5:14 pm, "Jorg Tiedemann" <[email protected] > <mailto:[email protected]>> wrote: > > Well, I have /opt/local/ search paths in various environment variables to get > macports to work. > I deleted all this paths and tried again but I still get the same problem. > > I am confused. And why is gcc not working anymore when installed via > macports? I also installed boost with macports. Is that a problem as well? > > I have also some problems with kenlm but part of it compiles and links fine. > build_binary and query seems to compile fine but lmplz does not link because > of some undefined symbols: > Undefined symbols for architecture x86_64: > > "boost::program_options::value_semantic_codecvt_helper<char>::parse(boost::any&, > std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, > std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> > > > const&, bool) const", > referenced from: > …. > > I also had to link /opt/local/lib to /opt/local/lib64 (which didn’t exist in > my setup). > I am afraid that I started to make quite a mess on my system but what did I > do wrong? > > Is macports not working properly anymore? > As I said, I have gcc 5.2.0 and boost 1.59.0 via macports on my system. Is > that bad? > > Thanks for helping! > Jörg > > > > >> On 31 Aug 2015, at 16:19, Hieu Hoang <[email protected] >> <mailto:[email protected]>> wrote: >> >> the errors for clang looks like it's coming from the stl library. Have you >> fiddled with the PATH variable or otherwise tried to make gcc on OSX work? >> You shouldn't do that, it will just mess up the compilation environment on >> your machine >> >> On 31/08/2015 10:28, Jorg Tiedemann wrote: >>> >>> Unfortunately, this didn’t work for me either. I attach both logiles - one >>> for clang and one for gcc (which I installed via macports) >>> What can I do? Thanks! >>> >>> Jörg >>> >>> >>> >>> >>> >>> >>> >>> >>>> On 30 Aug 2015, at 11:33, Hieu Hoang < >>>> <mailto:[email protected]>[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Add >>>> toolset=clang >>>> to the bjam compile command. Osx no longer has gcc >>>> >>>> Hieu Hoang >>>> Sent while bumping into things >>>> >>>> On 29 Aug 2015 11:56 pm, "Jorg Tiedemann" <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> Hi, >>>> >>>> I tried to make a fresh install of Moses on my new Mac and I get the >>>> following error >>>> g++: error: unrecognized command line option '-no-cpp-precomp' >>>> >>>> What’s wrong? I have gcc5 and boost 1.59 on my machine via macports ... >>>> >>>> Thanks for your help! >>>> Jörg >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moses-support mailing list >>>> [email protected] <mailto:[email protected]> >>>> http://mailman.mit.edu/mailman/listinfo/moses-support >>>> <http://mailman.mit.edu/mailman/listinfo/moses-support> >>>> >>>> _______________________________________________ >>>> Moses-support mailing list >>>> [email protected] <mailto:[email protected]> >>>> http://mailman.mit.edu/mailman/listinfo/moses-support >>>> <http://mailman.mit.edu/mailman/listinfo/moses-support> >>> >> >> -- >> Hieu Hoang >> Researcher >> New York University, Abu Dhabi >> http://www.hoang.co.uk/hieu <http://www.hoang.co.uk/hieu>
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
