Hi

I reported the following error for openmpi-1.9r28203 and did some research
in the meantime.

> Solaris 10, x86_64 and sparc, SunC 5.12, 32-bit and 64-bit
> ----------------------------------------------------------
> 
> sunpc1 openmpi-1.9-SunOS.x86_64.32_cc 16 tail -15 log.make.SunOS.x86_64.32_cc
> make[2]: Entering directory `.../opal/tools/wrappers'
>   CC       opal_wrapper.o
> "../../../../openmpi-1.9r28203/opal/include/opal/sys/ia32/atomic.h",
>   line 173: warning: parameter in inline asm statement unused: %2
> "../../../../openmpi-1.9r28203/opal/include/opal/sys/ia32/atomic.h",
>   line 193: warning: parameter in inline asm statement unused: %2
>   CCLD     opal_wrapper
> Undefined                       first referenced
>  symbol                             in file
> opal_hwloc152_hwloc_solaris_get_chip_model ../../../opal/.libs/libopen-pal.so
> opal_hwloc152_hwloc_solaris_get_chip_type ../../../opal/.libs/libopen-pal.so
> ld: fatal: symbol referencing errors. No output written to .libs/opal_wrapper
> make[2]: *** [opal_wrapper] Error 2
> make[2]: Leaving directory `.../opal/tools/wrappers'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `.../opal'
> make: *** [all-recursive] Error 1


The symbols hwloc_solaris_get_chip_model and hwloc_solaris_get_chip_type
are available in file
.../openmpi-1.9r28206/opal/mca/hwloc/hwloc152/hwloc/src/topology-solaris-chiptype.c


They are also known in the library, but the symbols with the prefix
opal_hwloc152_ are unknown.

tyr openmpi-1.9-SunOS.sparc.64_cc 152 cd 
opal/mca/hwloc/hwloc152/hwloc/src/.libs/
tyr .libs 153 nm libhwloc_embedded.a | grep get_chip
[145] |    0|   0|FUNC |GLOB |0 |UNDEF 
|opal_hwloc152_hwloc_solaris_get_chip_model
[146] |    0|   0|FUNC |GLOB |0 |UNDEF 
|opal_hwloc152_hwloc_solaris_get_chip_type
[28]  |  512| 256|OBJT |GLOB |0 |6     
|$XBnghrBxhwTRnTP.hwloc_solaris_get_chip_type.chip_type
[22]  | 3152| 220|FUNC |GLOB |2 |2     |hwloc_solaris_get_chip_model
[29]  | 2768| 356|FUNC |GLOB |2 |2     |hwloc_solaris_get_chip_type

Perhaps this information helps to track down the error.


Kind regards

Siegmar

Reply via email to