Whoa, I've been looking for an answer to this riddle myself. I'm not a program and do not have a clear grasp of what cmake does. Having said that, though, I wonder how Mac got around to installing the program since they also use clang in a (heavily modified) BSD environment as far as I know. Their instruction seems fairly straight forward; what are the differences in two methods? Could it be possible for us to "fool" cmake into giving us the same condition Mac gets?
On Monday, June 30, 2014 4:29:38 PM UTC+9, Jostein Berntsen wrote: > > > > On Monday, June 30, 2014 7:26:46 AM UTC+2, Chris Leyon wrote: >> >> Update: I've given up on clang. I never did figure out how to tell >> cmake and/or acprep to pass a new option like "-stdlib=..." to the >> compilation phase. I assume it's possible somehow. So I ended up >> grabbing the compilation commands cmake produced and copying them into >> a script and I manually added the option you suggested and recompiled. >> Then it complained about not finding several standard include library >> files. >> >> So I am now trying g++. Again, due to cmake >> >> > Can you try to compile with therse options for acprep? > > ./acprep --debug --python --compiler="g++-4.8.4 -lboost_regex > -lboost_iostreams" --boost=/your-boost-root-path > > Jostein > > > > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
