[llvm-bugs] [Bug 39189] New: Initial implementation of OMP 5.0 Memory Management routines makes use of libomp.a harder or even impossible

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=39189

            Bug ID: 39189
           Summary: Initial implementation of OMP 5.0 Memory Management
                    routines makes use of libomp.a harder or even
                    impossible
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Runtime Library
          Assignee: unassignedbugs at nondot.org
          Reporter: newchief at king.net.pl
                CC: llvm-bugs at lists.llvm.org

The https://reviews.llvm.org/D51232 commit is bit damaging for those who want
to use libomp.a for -static built applications. As KMP_DYNAMIC_LIB is hardcoded
to 1 in kmp_config.h.cmake, dlopen will always be used causing following
link-time warning:

warning: Using 'dlopen' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking

This makes virtually impossible to copy libomp.a across various Linux boxes or
shipping libomp.a in binary libomp packages addressed to various Linux systems.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20181005/1daa27dd/attachment.html>