This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Xerces-C: two issues with gcc4/cygwin-1.7

Charles Wilson wrote:
> Charles Wilson wrote:

>> src/CreateDOMDocument/CreateDOMDocument.o:CreateDOMDocument.cpp:(.gcc_except_table+0xe8):
>> undefined reference to `typeinfo for xercesc_3_0::XMLException'
>> src/CreateDOMDocument/CreateDOMDocument.o:CreateDOMDocument.cpp:(.gcc_except_table+0xf0):
>> undefined reference to `typeinfo for xercesc_3_0::DOMException'
>> collect2: ld returned 1 exit status
>> )
>> I checked the export list from the DLL, and there are NO typeinfo
>> symbols exported at all.  Does this appear to be a gcc4 bug, or is there
>> something specific I need to do to cause typeinfo stuff to be exported?

  In general they should be auto-exported like any other symbol.  It depends
if there are any dllexport annotations in play, which would cancel
auto-export.  There could also be compiler or linker problems, we'll need to
debug it.

> Just noticed something odd. libtool transforms the giant link command
> for the DLL, with hundreds of .lo files, into the following:
> g++ -shared -nostdlib /usr/lib/gcc/i686-pc-cygwin/4.3.2/crtbegin.o
> .libs/  -L/usr/lib /usr/lib/libcurl.dll.a
> /usr/lib/libssh2.dll.a -lssl -lcrypto -lz -licuuc -licudata
> -L/usr/lib/gcc/i686-pc-cygwin/4.3.2
> -L/usr/lib/gcc/i686-pc-cygwin/4.3.2/../../..
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/libstdc++.dll.a -lgcc_s -lgcc_s
> -lcygwin -luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc_s -lgcc_s
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/crtend.o    -o
> .libs/cygxerces-c-3-0.dll -Wl,--enable-auto-image-base -Xlinker
> --out-implib -Xlinker .libs/libxerces-c.dll.a
> Creating library file: .libs/libxerces-c.dll.a
> I've attached the link script. Could that make a difference, and cause
> the typeinfo to not be exported?

  No, that's standard libtool behaviour: ld doesn't understand the contents of
a .lo file, libtool parses them out, finds the actual PIC objects and builds a
list of input files to avoid passing over-long command-lines.

  Let's see the output for 'nm xercesc/util/.libs/XMLException.o'; that should
confirm whether the typeinfo got generated or not.  After that, we'll need to
find out if it's in the DLL but not exported, and whether auto-export is in
operation or not.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]