[llvm-bugs] [Bug 25666] New: requested re-export symbol std::set_unexpected(void (*)()) is not from a dylib, but from .../exception.cpp.o
via llvm-bugs
llvm-bugs at lists.llvm.org
Sun Nov 29 07:46:44 PST 2015
https://llvm.org/bugs/show_bug.cgi?id=25666
Bug ID: 25666
Summary: requested re-export symbol std::set_unexpected(void
(*)()) is not from a dylib, but from
.../exception.cpp.o
Product: libc++
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangbugs at nondot.org
Reporter: jeremyhu at apple.com
CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com
Classification: Unclassified
Created attachment 15360
--> https://llvm.org/bugs/attachment.cgi?id=15360&action=edit
build log (compressed)
Building recent master (r253905) on Lion and Mountain Lion through MacPorts
using my in-progress changes from autoconf to cmake, I am running into the
following error when linking libc++:
ld: requested re-export symbol std::set_unexpected(void (*)()) is not from a
dylib, but from CMakeFiles/cxx.dir/__/src/exception.cpp.o
We don't actually intend to *ship* this libc++.dylib. It's just being built
because of #25665.
This does not happen on El Capitan.
I have not yet tested on Mavericks or Yosemite.
--
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/20151129/ca9d6696/attachment-0001.html>
More information about the llvm-bugs
mailing list