[Edoc-main] Installation problems
Status: Beta
Brought to you by:
bjcosta
From: Will M. <wil...@us...> - 2008-06-27 16:10:25
|
Hello, I'm really, really anxious to try edoc out, but I'm having trouble. First, it doesn't compile on Mac OS due to a lack of libbfd. Interestingly, configure checks for libbfd but doesn't consider its absence a failure, even though the build will fail if libbfd is not there. This is probably a bug. Then I switched to FreeBSD. It took a little trickery to get the build to work. I had to create a symbolic link to /usr/local/lib/libpython2.5.so, since the edoc build only looks for libpython. Then, my configure invocation looks like this: LDFLAGS=-L/usr/local/lib CPPFLAGS=-I/usr/local/include/python2.5 LIBS=-lpthread ./configure Setting --with-libpython doesn't work, since you can't set it to /usr/local due to the location of the headers. Then the build failed because bfd_utils.cpp does not include <sys/stat.h>, even though it uses struct stat. It also fails while building gcc due to conflicting declarations of the function strsignal, which I resolved by commenting the edoc-included one out. Finally, with edoc successfully built on FreeBSD I get the following at every invocation: $ edoc Connection.hpp Filed opening file: Connection.hpp Reason: Unknown file type. $ It doesn't matter what input I give edoc. It will tell me that the file type is unknown in every instance, without fail, even if the input is a directory. Thanks for any help, Will |