From: Tomas Frydrych (tomasfrydrych_at_yahoo.co.uk)
Date: Thu Apr 29 2004 - 02:14:57 EDT
I have no idea what that should be; all I have done is to add 4
functions to ut_string.cpp, and even according to the error log the
entire libXap builds successfully -- perhaps the library has got too
many symbols for Mingw?
Tomas
> On Fri, 2004-04-23 at 21:09 +0100, Tomas Frydrych wrote:
> > a handfull of pre-processing directives allowing to turn off bidi and
> > shaping support at compile time by defining NO_BIDI_SUPPORT.
> >
> > files: ut_string.cpp, ut_Win32String.cpp, gr_ContextGlyph.h/cpp,
> > gr_RenderInfo.cpp, fp_TextRun.cpp, fp_Run.cpp
>
> For some reason, the changes in ut_string.cpp, ut_string.h or
> ut_Win32String.cpp causes the MinGW build to fail with:
>
> c:/src/abihead/src/MINGW32_1.0.10_i386_OBJ/obj/libAbiXAp.a(xap_ModuleManager.o)(.text+0x639):xap_ModuleManager.cpp: undefined reference to `XAP_Module::setSymbols(int (*)($_65*), int (*)($_65*), int (*)(unsigned, unsigned, unsigned))'
>
> MSVC builds are unaffected, so not sure if this is just a bug in MinGW
> or a compatibility issue. The MinGW tinderbox build is also having the
> same issue.
This archive was generated by hypermail 2.1.4 : Thu Apr 29 2004 - 02:16:20 EDT