On 05.07.14,05:20, y2s1982 . wrote:
> Thank you everyone for taking a stab at this problem.  Pity it wasn't
> resolved :(
> 
> I've tried to make acprep update to at least begin compiling and following
> changes helped me get there, though I still ran into the same problem while
> compiling output.cc as Chris mentioned.
> 
> First, looking at the following site: https://wiki.freebsd.org/NewC++Stack
> I've changed the CMakeLists.txt like the following:
> before: add_definitions(-std=c++11)
> after: add_definitions(-stdlib=libc++ -std=c++11)
> 
> That let me start compiling... and fail right away on account that
> editline/readline.h doesn't exist.
> Well, turns out, in FreeBSd,
> http://www.freebsd.org/cgi/man.cgi?query=readline&apropos=0&sektion=3&manpath=FreeBSD+10.0-RELEASE&arch=default&format=html
> the file exists in readline/readline.h
> So, I've changed system.hh by changing #include <editline/readline.h> to
> #include <readline/readline.h>
> 
> That allowed me to continue further until output.cc error occurs.
> 
> As for boost regex, that also exists in the system, though I do get the
> error message mentioned before. I did find the boost/regex/icu.hpp. I've
> tried forcing the system to use the boost/regex/icu by editing system.hh,
> but I still had the same problem with output.cc
> 
> Any other suggestions?  I'm still willing to work with clang if possible.
> Does OS X still use the gcc extension or are they making it to work with
> clang?
> 
> 

Could you try compiling with acprep and before this change the
add_definitions line in CMakeLists.txt to this instead?

add_definitions(-stdlib=libstdc++ -std=c++11)

Or try the solutions from Ronald Ip in this previous post?

https://groups.google.com/d/msg/ledger-cli/Yn_d8qO3iBM/f288sE0kQrIJ

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.

Reply via email to