PATHANGI JANARDHANAN JATINSHRAVAN wrote:
This was my configure command: $ ./configure --enable-category-b
--enable-wiki-publisher --enable-bundled-dictionaries
--without-stlport
--with-dmake-url=http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2
--with-epm-url=http://www.msweet.
This was my configure command:
$ ./configure --enable-category-b --enable-wiki-publisher
--enable-bundled-dictionaries --without-stlport
--with-dmake-url=http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2
--with-epm-url=http://www.msweet.org/files/project2/epm-3.7-source.tar.
AOO should automatically download, build and use an internal OpenSSL.
Please show the configure options you used (they're saved at the top of
config.log).
On Sun, Nov 15, 2015 at 3:05 PM, #PATHANGI JANARDHANAN JATINSHRAVAN# <
jatinshr...@e.ntu.edu.sg> wrote:
> Yes, I did run a make clean from the
Yes, I did run a make clean from the root dir, and it did work later, but I
think some of the documentation needs to be updated to reflect the changes that
happened in OS X 10.11
I ran into issues with openssl because Apple removed openssl headers from OS X
with the release of El Capitan. I had
On 13/11/2015 #PATHANGI JANARDHANAN JATINSHRAVAN# wrote:
Why is only this module replacing 10.11 with 10.10 during the build process?
Did you try with a fully clean build, i.e., recreating everything from
scratch? If you have some old paths around this could be a leftover from
the previous co
As a follow up to the previous email, my MAC_OSX_SDK_PATH environment variable
is as follows:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.
11.sdk
And my LIBXML_CFLAGS is
I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Develo
