similar to: [LLVMdev] Building front end under OS X

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 >

I've tried llvm 2.8 and 2.9, but they both have problems with #include <iosfwd>. Any pointers to what this might be? /usr/include/c++/4.5/iosfwd:39:10: fatal error: 'bits/c++config.h' file not found #include <bits/c++config.h> -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/

sorry ! I have re-corrected the title. ------------------ 原始邮件 ------------------ 发件人: "Sheng Wang"<wansheg at gmail.com>; 发送时间: 2009年9月4日(星期五) 下午3:23 收件人: "LLVMdev"<LLVMdev at cs.uiuc.edu>; 主题: [LLVMdev] Dose I need to build llvm-gcc front-end from sourceresolve this error? /* mm.cpp */ #include<iostream> using namespace std; struct xx{ int x;

Index: include/llvm/ADT/APInt.h =================================================================== --- include/llvm/ADT/APInt.h (revision 55101) +++ include/llvm/ADT/APInt.h (working copy) @@ -20,6 +20,7 @@ #include <cassert> #include <iosfwd> #include <string> +#include <cstring> namespace llvm { class Serializer; -------------- next part -------------- An

Hi list, Here it is: I have compiled with no problem courier-imap-4.0.4 on this arch (x86_64). Now I want to update my install with 4.0.6. I want to do this because the server is not yet in a production state, so if a major flaw affects courier-imap in the future, I could react more quickly. And indeed I'm encountering problems with the make process (Since I initialy build courier-imap

Please commit. On Aug 20, 2008, at 8:02 PM, Zhongxing Xu wrote: > Index: include/llvm/ADT/APInt.h > =================================================================== > --- include/llvm/ADT/APInt.h (revision 55101) > +++ include/llvm/ADT/APInt.h (working copy) > @@ -20,6 +20,7 @@ > #include <cassert> > #include <iosfwd> > #include <string> >

> Sorry, I meant from which version of clang? I'm using Ubuntu 10 and > I was wondering if clang/llvm 2.8 would do it. Perhaps I better try the latest, got an error when I tried 2.8: In file included from testsuite/test.cpp:8: In file included from ./testsuite/precompile.h:4: ./util/precompile.h:17:12: fatal error: 'iosfwd' file not found -- Øyvind Harboe - Can Zylin

Hi, I am new to LLVM, so I am sorry if the question I am going to ask has already been raised before. I will be thankful if anyone can describe me a quick way to search relevant topics within the list archive, When I am trying to compile a simple code, containing access to std::string, with clang: #include <string> int main() { std::string s; return

When building LLVM (trunk) on macOS (where there is no /usr/include/), the resulting Clang works fine for me when I add an appropriate -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk to the command line when invoking Clang. (I'm not sure I'm using it as intended, but that appears to work reasonably well for me.) However, when

/* mm.cpp */ #include<iostream> using namespace std; struct xx{ int x; int mm()const; int mm(); }; int xx::mm() const { return const_cast<xx*>(this)->mm(); } int xx::mm() { cout<<"ok"<<endl; return x; } int main() { xx x; x.mm(); return 0; }

Hello, I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have our own gcc compiler that we build with crosstools-ng (based on gcc 6.3.0) and I set my environment like this: CC=armv7a-plex-linux-gnueabihf-gcc CXX=armv7a-plex-linux-gnueabihf-g++ CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16 --sysroot=<path> CXXFLAGS=-fPIC -DPIC

cmake -E cmake_progress_report llvm-3.8.0.src_bld_x86_64-rhel6.4-linux-gnu/CMakeFiles In file included from llvm-3.8.0.src/projects/libcxx/include/__hash_table:19:0, from llvm-3.8.0.src/projects/libcxx/src/hash.cpp:10: llvm-3.8.0.src/projects/libcxx/include/cmath:310:9: error: '::signbit' has not been declared using ::signbit; ^

At first glance, it looks like long double functions (such as fabsl and friends) are missing from your sysroot's <math.h>. Does your target support long double at all? -Dimitry > On 6 Feb 2018, at 09:51, Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > > I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have

Hello Dimitry and thanks for your answer. I am pretty sure it does indeed support long double. It's configured with vfpv3-d16 - but I noticed that c++config.h in gcc has _GLIBCXX__HAS_FABSL and friends are undefined. I think I need to look deeper at the configuration of our toolchain. long double support is required in libc++ then I gather? -- Tobias On Tue, Feb 6, 2018 at 11:47 AM,

On Mon, 25 Oct 2004, Morten Ofstad wrote: > several of the patches I submitted last week have not yet been applied, > and most of it was really uncontroversial stuff like adding some > #includes and some typecasts, fixing alloca for visual C etc. Oops, sorry about that. :( > I guess I just wrote too many mails so it was lost in the process, so > here is a diff which includes all

Greetings! I have been building llvm-3.6.x, 3.7.1 and 3.7.2 with (glibc-2.12.1, binutils-2.24, gcc-4.9.2) almost same set if CMake flags. However while building LLVM-3.8.0 using same CMake flags I am observing projects/libcxx/include/cmath errors... ...'::signbit' has not been declared ...'::fpclassify' has not been declared ...'::isfinite' has not been declared ...

Hi Brian Here's the config.log (I'm not posting it on the dev-list). The automatic gcc macro for Interix is __INTERIX if this is to any help. /Henrik >From: "Brian R. Gaeke" <gaeke at uiuc.edu> >Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >Subject: Re: [LLVMdev]

If you have not done so, you have to configure a clang header to find your default libc++ header files. See #5 at http://clang.llvm.org/get_started.html if this is your issue. Garrison On Jun 30, 2011, at 10:33, Øyvind Harboe wrote: > I've tried llvm 2.8 and 2.9, but they both have problems with > #include <iosfwd>. > > Any pointers to what this might be? > >

Hi >From: Chris Lattner <sabre at nondot.org> >Date: Thu, 15 Jul 2004 17:43:27 -0500 (CDT) >Ah, suddenly everything makes sense. If you're interested in LLVM on the >windows platform, *please* get CVS. Last night I've got the latest version of LLVM from CVS and now porting LLVM to Interix from this version on. I got this error: --------------------- gmake[1]:

Thanks for responding, Duncan, and clarifying that y'all need more info to help. I'm trying to compile binaries on os x 10.5.8 intel hardware that are compatible on ppc os x 10.4. When I include various flags to llvm-gcc, including: -m32 -arch ppc -isysroot /Developer/SDKs/MacOS10.4u.sdk -mmacosx-version-min=10.4 I am seeing errors when compiling using llvm-gcc 4.2. If I leave out