Dear Alan,
On 30.11.2016 21:48, Alan W. Irwin wrote:
> On 2016-11-30 20:06+0100 Mario Emmenlauer wrote:
> [...]
>> The symbol is defined in libvtkCommonCore-7.1.dll:
>> nm ../../bin/libvtkCommonCore-7.1.dll | c++filt | grep
>> 'vtkAOSDataArrayTemplate<unsigned char>::FastDownCast(vtkAbstractArray.*)'
>>
>> 0000000066bd10e0 T vtkAOSDataArrayTemplate<unsigned
>> char>::FastDownCast(vtkAbstractArray*)
>>
>> Am I missing something about linkage on Windows/MinGW?
>
> If nm shows the symbol is defined, yet the linker cannot see it, then
> that is very likely due to a symbol visibility issue. To check
> that compare results for
>
> nm --defined-only
>
> which only lists symbols that are defined by the library
>
> and
>
> nm --defined-only --extern-only
>
> which only lists symbols that are both defined by the library and
> externally visible. If your "missing" symbol is on the first list
What you say makes perfect sense and is interesting to learn, thanks!
To my confusion however, the symbol seems defined and present in both
restrictions. I tried all combinations, here the intersection as an
example:
#> nm --defined-only --extern-only ../../bin/libvtkCommonCore-7.1.dll | c++filt
| grep 'vtkAOSDataArrayTemplate<unsigned
char>::FastDownCast(vtkAbstractArray.*)'
0000000066bd10e0 T vtkAOSDataArrayTemplate<unsigned
char>::FastDownCast(vtkAbstractArray*)
Whats more: there are like a hundred undefined symbols in objects.a,
so it certainly must find quite a lot of them in some of the dlls,
otherwise I'd get more errors, would I not? Does that make any sense?
Am I maybe overlooking something?
Cheers,
Mario
------------------------------------------------------------------------------
_______________________________________________
Msys2-users mailing list
Msys2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msys2-users
