Idea about libstdc++ headers support

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Idea about libstdc++ headers support

Konstantin Tokarev
Hi all,

"Getting Started" suggests patching of source code in case "Clang cannot find your system libstdc++ headers".
Maybe it's reasonable to add optional configuration file with path to libstdc++ headers? (e.g., Intel compiler also
has configuration file for user settings)

--
Regards,
Konstantin
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: Idea about libstdc++ headers support

Anton Korobeynikov
Hello

> "Getting Started" suggests patching of source code in case "Clang cannot find your system libstdc++ headers".
> Maybe it's reasonable to add optional configuration file with path to libstdc++ headers? (e.g., Intel compiler also
> has configuration file for user settings)
Yes if done properly. Look into
http://clang.llvm.org/UniversalDriver.html for a proposal. Noone was
brave enough to start this project :)

--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: Idea about libstdc++ headers support

Marc Glisse
In reply to this post by Konstantin Tokarev
On Mon, 21 Mar 2011, Konstantin Tokarev wrote:

> "Getting Started" suggests patching of source code in case "Clang cannot
> find your system libstdc++ headers".

And some people find it much better to use:

.../llvm/configure --with-cxx-include-root=/usr/include/c++/4.2 --with-cxx-include-arch=x86_64-linux-gnu --with-cxx-include-32bit-dir=32 --with-cxx-include-64bit-dir=""

i.e. put the same information on the command line instead of patching a
file. Besides, this also helps in the case where clang finds *several*
libstdc++ headers and is too greedy to just pick one and stick to it.

--
Marc Glisse
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev