Hi

This is the output from the third run of "make". I can make the Xalan.exe 
separately from the makefile in src/xalanc, but I get the same info messages 
about resolving entities in the DLL. This is from running make in XALANCROOT.

Ian

$ make
make -C src/xalanc all
make[1]: Entering directory `/xalan/src/xalanc'
Preparing the directory structure for a build ...
mkdir -p ../../obj
mkdir -p ../../lib
mkdir -p ../../bin
make -C Utils prepare
make[2]: Entering directory `/xalan/src/xalanc/Utils'
mkdir -p ../../../nls
mkdir -p ../../../nls/include
make[2]: Leaving directory `/xalan/src/xalanc/Utils'
make -C Utils locale
make[2]: Entering directory `/xalan/src/xalanc/Utils'
make[2]: Nothing to be done for `locale'.
make[2]: Leaving directory `/xalan/src/xalanc/Utils'
g++ -O -DNDEBUG  -mthreads   -fno-elide-constructors -DWIN32 -D_WINDOWS 
-D__MINGW__ -DMINGW -fexceptions -DXALAN_INMEM_MSG_LOADER -c -I/xalan/src 
-I/xalan/include -I../../nls/include -I/xerces/src/ -I/xerces/include/xercesc 
-I/xerces/include/  -o ../../obj/process.o 
/xalan/src/xalanc/TestXSLT/process.cpp
g++ -DMINGW -mthreads -Wl,--allow-multiple-definition -DXALAN_INMEM_MSG_LOADER \
         -L../../lib -L/xalan/lib -lxalan-c -lm  -mthreads  -L/xerces/lib 
-lxerces-c -L../../lib -lxalanMsg ../../obj/process.o -o ../../bin/testXSLT   
-L../../lib -L/xalan/lib -lxalan-c -lm  -mthreads  -L/xerces/lib -lxerces-c 
-L../../lib-lxalanMsg
Info: resolving xalanc_1_11::XalanDOMString::s_empty       by linking to 
__imp___ZN11xalanc_1_1114XalanDOMString7s_emptyE (auto-import)
Info: resolving vtable for xalanc_1_11::XSLTInputSource by linking to 
__imp___ZTVN11xalanc_1_1115XSLTInputSourceE (auto-import)
Info: resolving xercesc_3_1::XMLUni::fgXercescDefaultLocale       by linking to 
__imp___ZN11xercesc_3_16XMLUni22fgXercescDefaultLocaleE (auto-import)
e:/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: warning: 
auto-importing has been activated without --enable-auto-import specified on the 
command line.
This should work unless it involves constant data structures referencing 
symbols from auto-imported DLLs.
g++ -O -DNDEBUG  -mthreads   -fno-elide-constructors -DWIN32 -D_WINDOWS 
-D__MINGW__ -DMINGW -fexceptions -DXALAN_INMEM_MSG_LOADER -c -I/xalan/src 
-I/xalan/include -I../../nls/include -I/xerces/src/ -I/xerces/include/xercesc 
-I/xerces/include/  -o ../../obj/TestXPath.o 
xalan/src/xalanc/TestXPath/TestXPath.cpp
g++ -O -DNDEBUG  -mthreads   -fno-elide-constructors -DWIN32 -D_WINDOWS 
-D__MINGW__ -DMINGW -fexceptions -DXALAN_INMEM_MSG_LOADER -c -I/xalan/src 
-I/xalan/include -I../../nls/include -I/xerces/src/ -I/xerces/include/xercesc 
-I/xerces/include/  -o ../../obj/NodeNameTreeWalker.o 
/xalan/src/xalanc/TestXPath/NodeNameTreeWalker.cpp
g++ -DMINGW -mthreads -Wl,--allow-multiple-definition -DXALAN_INMEM_MSG_LOADER \
         -L../../lib -L/xalan/lib -lxalan-c -lm  -mthreads  -L/xerces/lib 
-lxerces-c -L../../lib -lxalanMsg -O -DNDEBUG  -mthreads   
-fno-elide-constructors ../../obj/TestXPath.o ../../obj/NodeNameTreeWalker.o -o 
../../bin/testXPath-L../../lib -L/xalan/lib -lxalan-c -lm  -mthreads  
-L/xerces/lib -lxerces-c -L../../lib -lxalanMsg
Info: resolving xalanc_1_11::XalanDOMString::s_empty       by linking to 
__imp___ZN11xalanc_1_1114XalanDOMString7s_emptyE (auto-import)
Info: resolving xercesc_3_1::XMLPlatformUtils::fgMemoryManager        by 
linking to __imp___ZN11xercesc_3_116XMLPlatformUtils15fgMemoryManagerE 
(auto-import)
Info: resolving xercesc_3_1::XMLUni::fgXercescDefaultLocale       by linking to 
__imp___ZN11xercesc_3_16XMLUni22fgXercescDefaultLocaleE (auto-import)
e:/mingw/bin/../lib/gcc/mingw32/4.4.0/../../../../mingw32/bin/ld.exe: warning: 
auto-importing has been activated without --enable-auto-import specified on the 
command line.
This should work unless it involves constant data structures referencing 
symbols from auto-imported DLLs.
g++ -O -DNDEBUG  -mthreads   -fno-elide-constructors  -mthreads 
-Wl,--allow-multiple-definition  /xalan/src/xalanc/TestXPath/testXPath.cpp lib 
../../bin/testXPath   -o testXPath
g++.exe: lib: No such file or directory
g++.exe: ../../bin/testXPath: No such file or directory
make[1]: *** [testXPath] Error 1
make[1]: Leaving directory `/xalan/src/xalanc'
make: *** [all] Error 2




________________________________
From: David Bertoni <dbert...@apache.org>
To: xalan-c-users@xml.apache.org
Sent: Sat, 6 March, 2010 18:59:40
Subject: Re: msys/mingw

On 3/4/2010 6:47 AM, ian balanza-davis wrote:
>
> Hi
>
> I downloaded xalan 1.11 from trunk and followed the instructions from
> the xalan website (for 1.10) to start with.
>
> I am using mingw version 4.4.0 and the current msys, whatever that
> version is.
>
> I have Xerces downloaded and built in /xerces ==> XERCESCROOT=/xerces
> (ie, the top level folder containing "src")
> I have Xalan downloaded and (trying to build) in /xalan ==>
> XALANCROOT=/xalan (ie, the top level folder containing "src")
>
>  From /xalan I use ./runConfigure -p mingw-msys -c gcc -x g++
> That seems to run fine, and then I run make.
>
> Knowing about the linker problems, I run make and create the
> libxalanMsg.dll symlink
> Run it a second time and create the libxalan-c.dll symlink, both
> pointing to the version-numbered libraries.
Hmm, I had a fix for these problems with msys Make utility, and I 
thought I committed it, but perhaps not.

>
> I do not have any .a or .la files. However hidden in the output for the
> libxalan-c1_11_0.dll file is the line
> "E:\mingw\bin\dllwrap.exe: no export definition file provided."
> I am not building with ICU as far as I am aware (I don't want to so I
> hope not) -- unless that is the default.
I don't think this is a problem, since the export macros take care of 
exporting everything.

> When I try make for a third time, I get the error mentioned below, plus
> plenty of others in the same vein.
>
> "xalan/src/xalanc/TestXPath/testXPath.cpp:19:50: error:
> xalanc/Include/PlatformDefinitions.hpp: No such file or directory"
Can you reply with a copy and paste of the full compiler command line 
for one of the files that won't build? I'm curious as to what the -I 
options look like.

Dave



      

Reply via email to