Bug 230185 - devel/llvm60: clang++60 failed to include standard header files if '-stdlib=libstdc++' option is specified
Summary: devel/llvm60: clang++60 failed to include standard header files if '-stdlib=l...
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Brooks Davis
URL:
Keywords:
Depends on: 230184
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-30 09:28 UTC by Yasuhiro Kimura
Modified: 2018-08-02 14:59 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (brooks)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yasuhiro Kimura freebsd_committer freebsd_triage 2018-07-30 09:28:25 UTC
Problem reported as bug #230184 also happens with devel/llvm60. And though I don't checked it is very likely this problem happens with other version of LLVM.
Comment 1 Brooks Davis freebsd_committer freebsd_triage 2018-07-30 16:27:49 UTC
I don't expect this to work.  You almost certainly need to specify the path to libstdc++'s headers manually.
Comment 2 Mark Millard 2018-07-30 23:30:53 UTC
So far as I know llvm does not provide the source to a
libstdc++. Some port would be required to supply the
source code for -stdlib=libstdc++ to find and use.

(For FreeBSD "builworld" and such there are licensing
issues for libstdc++. Thus a port likely being involved.)
Comment 3 Brooks Davis freebsd_committer freebsd_triage 2018-08-02 14:59:25 UTC
I won't be fixing this.  To fix it reliably, we'd have to provide a dependency on a gcc port to provide a libstdc++ in a known location and patch the -stdlib=libstdc++ code to match.  If want libstdc++, use gcc.