On Mon, Jan 10, 2011 at 5:23 PM, Marko Kocić <marko.ko...@gmail.com> wrote:
> I can see that it is populated by configure, but I don't know how to > create a patch for this. I suppose -lffi should be added there when > ffi is detected, or maybe the right place is CORE_LIBS? > Sorry, I missed the previous email and I can not find it in my gmail account. Was it properly sent? Note that your email lists two different problems. The first one is that libffi is not included in the flags. In order to do so you should build and install the library in a "standard" location, one which is found by gcc and ld. Either that or supply the appropriate CPPFLAGS (for the headers) and LDFLAGS (for the library). Inspection of config.log will tell you whether configure (autoconf's standard processes) found the library. The second problem is related to sockets. But note that you are building ECL using g++, not a C compiler. C++ compilers may be too strict for some of the C inline code that is in sockets. In particular it seems that the type conversions that are used do not work -- I am unsure about this, but ECL seems to build just fine with a C++ compiler on other platforms. Maybe the internet headers are different on Mingw :-/ Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
