[llvm-bugs] [Bug 34040] New: "error: ‘__va_copy’ was not declared in this scope" while building libomp against musl libc

[via llvm-bugs]

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

            Bug ID: 34040
           Summary: "error: ‘__va_copy’ was not declared in this scope"
                    while building libomp against musl libc
           Product: OpenMP
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Runtime Library
          Assignee: unassignedbugs at nondot.org
          Reporter: plevine457 at gmail.com
                CC: llvm-bugs at lists.llvm.org

Building libomp-3.9.0 in Gentoo Linux with musl as libc using GCC-6.3.0 or
GCC-5.4.0 results in:

> /var/tmp/portage/sys-libs/libomp-3.9.0/work/openmp-3.9.0.src/runtime/src/kmp_str.c:211:40: error: ‘__va_copy’ was not declared in this scope
>                  __va_copy( _args, args );  // Make copy of args.
>                                         ^

musl had previously provided "__va_copy" but has since relegated it only for
scenarios in which "__GNUC__ < 3", in favor of using "va_copy" (see
http://git.musl-libc.org/cgit/musl/commit/?id=def0af189871a499efdc9bc37438d8b20eb702ab).


Seeing as libomp source code already uses one-line, double-slash style comments
which require at least C99 dialect, and that va_copy is a C99 macro, the best
course of action would be to change "__va_copy" to "va_copy".

-- 
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/20170803/8c809567/attachment.html>