When built using the guidelines in the README.LLVM to use the system's libstdc++ I get the following types of errors whenever I try to use the standard library (say by running the front end test suite in llvm/test): /usr/include/c++/4.0.0/cmath:49:28: error: bits/c++config.h: No such file or directory /usr/include/c++/4.0.0/iosfwd:45:29: error: bits/c++locale.h: No such file or directory /usr/include/c++/4.0.0/iosfwd:46:25: error: bits/c++io.h: No such file or directory /usr/include/c++/4.0.0/bits/atomicity.h:38:30: error: bits/ atomic_word.h: No such file or directory Is this a product of the system's libstdc++ getting out of date w.r.t. the llvm-gcc tip? Should one now be building llvm-gcc's libstdc ++ rather than using the system version on OS X? -- Christopher Lamb -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070422/2808e704/attachment.html>
On Sun, 22 Apr 2007, Christopher Lamb wrote:> When built using the guidelines in the README.LLVM to use the system's > libstdc++ I get the following types of errors whenever I try to use the > standard library (say by running the front end test suite in llvm/test): > > /usr/include/c++/4.0.0/cmath:49:28: error: bits/c++config.h: No such file or > directory > /usr/include/c++/4.0.0/iosfwd:45:29: error: bits/c++locale.h: No such file or > directory > /usr/include/c++/4.0.0/iosfwd:46:25: error: bits/c++io.h: No such file or > directory > /usr/include/c++/4.0.0/bits/atomicity.h:38:30: error: bits/atomic_word.h: No > such file or directoryI'm not sure. This is strange, perhaps others will have a better idea.> Is this a product of the system's libstdc++ getting out of date w.r.t. the > llvm-gcc tip? Should one now be building llvm-gcc's libstdc++ rather than > using the system version on OS X?When building on macosx, you always want to remove the libstdc++ directory out of the llvm-gcc srcdir (so that you build with the system libstdc++). This is because the system version and the llvm-gcc version are subtly different, so you end up with abi mismatches if you don't. -Chris -- http://nondot.org/sabre/ http://llvm.org/
On Apr 22, 2007, at 3:43 PM, Chris Lattner wrote:> On Sun, 22 Apr 2007, Christopher Lamb wrote: >> When built using the guidelines in the README.LLVM to use the >> system's >> libstdc++ I get the following types of errors whenever I try to >> use the >> standard library (say by running the front end test suite in llvm/ >> test): >> >> /usr/include/c++/4.0.0/cmath:49:28: error: bits/c++config.h: No >> such file or >> directory >> /usr/include/c++/4.0.0/iosfwd:45:29: error: bits/c++locale.h: No >> such file or >> directory >> /usr/include/c++/4.0.0/iosfwd:46:25: error: bits/c++io.h: No such >> file or >> directory >> /usr/include/c++/4.0.0/bits/atomicity.h:38:30: error: bits/ >> atomic_word.h: No >> such file or directory > > I'm not sure. This is strange, perhaps others will have a better > idea. > >> Is this a product of the system's libstdc++ getting out of date >> w.r.t. the >> llvm-gcc tip? Should one now be building llvm-gcc's libstdc++ >> rather than >> using the system version on OS X? > > When building on macosx, you always want to remove the libstdc++ > directory > out of the llvm-gcc srcdir (so that you build with the system > libstdc++). > This is because the system version and the llvm-gcc version are subtly > different, so you end up with abi mismatches if you don't.Ahh. Well, with the SVN version of libstc++ the llvm/tests front end tests now pass, but ABI mismatches are a sinker... -- Christopher Lamb -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070422/ac7ce069/attachment.html>