-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auth branch does not compile on Linux #111
Comments
@emilis: It turns out that (at least on Ubuntu) the CMake file for Curl is called FindCURL, not Findcurl. If you change A side note: After changing this, I still couldn't compile the |
@Aaron1011 fogleman already fixed the CURL dependency. Now I am also stuck with the libbsd problem. Searched a little bit: it seems there is no Find...cmake file for libbsd. Not sure how to work around this, since I have no experience with CMake. |
Don't worry about libbsd, I'll use something other than strlcat |
@fogleman Was searching for some CMake hack. Stopped searching. Now waiting for a commit :) |
Fixed, so closing. |
I have a similar CURL problem on Linux Mint 14 (I have curl installed) cmake .
To solve had to install libcurl: sudo apt-get install libcurl4-openssl-dev |
Hello, I build it success as your tip! But when I use ./craft to run it on ubuntu12.04 LTS, occured Segmentation fault (core dumped), how to solve it ? thank you! hl@lilei: |
@FanChael Could you provide a backtrace or core dump? Might help in reproducing the problem. Simplest way is to
(although I'm not sure the makefile compiles in debug symbols by default, so you might have to change that too.) |
I have the same problem. Compiled on Ubuntu 12.04 and the program immediately crashes with a segmentation violation. Here is some info, as per the request above (I added the -g flag when compiling). BOLO: gdb ./craft Program received signal SIGSEGV, Segmentation fault. I'd love to get this working to do some hobby AI... ;-) Thanks in advance. |
auth
branch with last commit being 27eae8d (more auth)The text was updated successfully, but these errors were encountered: