Hi,
for what it is worth, just a note as I encountered relocation errors while
compiling VTK and Paraview seemingly due to linking shared libraries to
non-PIC static libraries.
- All the objects had been compiled with -fPIC.
- Passing -mimpure-text to GCC to ignore the linker error (removing -z text
from the flags passed to ld) leads to immediate segmentation fault.
- Disabling visibility allowed to build a functioning library.
Text relocation remains referenced
against symboloffsetin file
std::_Rb_treevtkVariant, std::pairvtkVariant const, int,
std::_Select1ststd::pairvtkVariant const, int , std::lessvtkVariant,
std::allocatorstd::pairvtkVariant const, int
::_M_erase(std::_Rb_tree_nodestd::pairvtkVariant const, int *)
0x3bf3CMakeFiles/vtkInfovisCore.dir/vtkReduceTable.cxx.o
std::_Rb_treevtkVariant, std::pairvtkVariant const, int,
std::_Select1ststd::pairvtkVariant const, int , std::lessvtkVariant,
std::allocatorstd::pairvtkVariant const, int
::_M_erase(std::_Rb_tree_nodestd::pairvtkVariant const, int *)
0x428eCMakeFiles/vtkInfovisCore.dir/vtkReduceTable.cxx.o
ld: fatal: relocations remain against allocatable but non-writable sections
collect2: error: ld returned 1 exit status
Is GCC visibility known to be broken with Solaris/Illumos ld ?
Best regards,
Aurelien
--
---
LARCHER Aurélien | KTH, School of Computer Science and
Communication
Work: +46 (0) 8 790 71 42 | Lindstedtsvägen 5, Plan 4, 100 44 Stockholm,
SWEDEN
---
___
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev