e.g.
main.cpp:1:10: fatal error: 'iostream' file not found
On Nov 01, 2012, Kostya Serebryany <k...@google.com> wrote:
+samsonovI think it's time to get rid of this #include <new> completely...On Thu, Nov 1, 2012 at 7:12 PM, st...@steck.com <st...@steck.com> wrote:Hello Clanger's,
When trying to build Clang on a standard Amazon Linux instance in the AWS cloud I received this error:
COMPILE: clang_linux/asan-x86_64/x86_64: /home/ec2-user/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc
/home/ec2-user/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:20:10: fatal error:
'new' file not found
#include <new>
^
1 error generated.
I tried resolving with --with-gcc-toolchain and other config, command line, and environment options but was unable to get it to work, so I resorted to a patch.
The patch is attached; can someone arrange to review and have the patch checked in if appropriate. All regression tests worked on both x86_64 and i686 architectures running Amazon Linux.
Cheers,
Steve Steck
_______________________________________________
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
_______________________________________________ cfe-commits mailing list cfe-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
- [cfe-commits] Can't Build Clang on AWS Amazon Linux Inst... st...@steck.com
- Re: [cfe-commits] Can't Build Clang on AWS Amazon L... Kostya Serebryany
- Re: [cfe-commits] Can't Build Clang on AWS Amaz... st...@steck.com
Reply via email to
