similar to: [LLVMdev] LLVM-gcc for Ada

Hi Eric, > llvm-main.o: In function `__static_initialization_and_destruction_0': > /usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/iostream:77: > undefi\ > ned reference to `std::ios_base::Init::Init()' > /usr/lib/gcc/i386-redhat-linux/4.3.2/../../../../include/c++/4.3.2/iostream:77: > undefi\ > ned reference to `std::ios_base::Init::~Init()'

Hi guys Is some one able to explain me, why these errors emerge: gmake[2]: Entering directory `/usr/local/src/llvm/lib/VMCore' Compiling AsmWriter.cpp AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const llvm::Constant*, bool, std::map<const llvm::Type*, std::string, std::less<const llvm::Type*>, std::allocator<std::pair<const llvm::Type* const,

No, Chris, I'm not buying that argument, due to I've tweaked /usr/include/types.h a little bit, so the configuration and compilation of the cfrontend would be correct: /* * 64bit type for BSD compatability */ #ifdef __GNUC__ typedef long long int quad_t; typedef unsigned long long int u_quad_t; typedef long long int int64_t; typedef unsigned long long int u_int64_t;

On Wed, 7 Jul 2004, Henrik Bach wrote: > This tweak seems to work. > > As far as I can see, correct me if I'm wrong, it is the compiler, that can't > figure out which std::basic_ostream to use. Why? What I'm saying is that it appears that your implementation of operator<< is not functional or is missing. You said that you are using GCC on internix. Is it possible

Yes, Chris you're right. It seems that my << operator for int64_t is missing in my '/opt/gcc.3.3/include/c++/3.3/bits/ostream.tcc' file. Which ordinary version of GCC are you working with and how do your definition of the << operator for int64_t look like? /Henrik > >Here is an excerpt from the config.log for LLVM: > >configure:19451: checking for int64_t

This is a forward of a question from the SourceForge LLVM forum. If anyone has experience with Cygwin and building the C front-end there, please reply and CC Alex. --- Post by Alex Vinokur below --- =============== Windows 2000 GNU gcc 3.3.3 (cygwin special) =============== ./configure ./make I have got compilation error ------------------------------- make[1]: Entering directory

How to solve this problem? $ make make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[1]: Leaving directory `/tmp/llvm3/llvm/build/libiberty' make[1]: Entering directory

Hi, in trying to build an llvm-gfortran on linux from today's gcc4 SVN, I get the following link errors that didn't show up on OS X. This is also using LLVM CVS from this morning. They appear to mostly be related to CodeWarrior compatibility code, but a couple are less obvious. What's the best way to fix this? I'm stuck without my powerbook for at least three weeks and I'd

Hi everyone, I am using linux/ppc and after porting llvm's jit for this architecture, I am currently trying to compile llvm-gcc on it. I have gcc 4.1.1 and use llvm-gcc from cvs. Compilation fails and the message is: gcc -O2 -DIN_GCC -DDEFAULT_TARGET_MACHINE=\"powerpc-unknown-linux-gnu\" -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long

Dear R-SIG-Debians, I have difficulties installing packages from within R through install.packages(). R version is 3.2.0 and OS is Linux Mint 17.1. For most packages, a lot of error messages come up which seem to be related to compilation. Installing packages provided by the ubuntu distro through apt-get works just fine. I followed all directions given in CRAN's

Hi, After a svn/cvs update I get the following errors when building the frontend. Anyone that sees the same ? http://gcc.gnu.org/svn/gcc/branches/apple/trunk/gcc/expr.h /* APPLE LOCAL begin radar 4441049 */ extern tree objc_v2_component_ref_field_offset (tree exp); extern tree objc_v2_bitfield_ivar_bitpos (tree exp); /* APPLE LOCAL end radar 4441049 */ mentions APPLE, is it only working on

On x86-64 linux, in stage 2, I get: c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ fortran/arith.o fortran/array.o fortran/bbt.o fortran/check.o fortran/data.o fortran/decl.o

On Wednesday 30 July 2008 18:13:27 Duncan Sands wrote: > On x86-64 linux, in stage 2, I get: > > c++ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -o f951 \ > fortran/arith.o

Here is an excerpt from the config.log: configure:19451: checking for int64_t configure:19476: gcc -c -g -O2 conftest.c >&5 configure:19479: $? = 0 configure:19482: test -s conftest.o configure:19485: $? = 0 configure:19496: result: yes configure:19511: checking for uint64_t configure:19536: gcc -c -g -O2 conftest.c >&5 configure:19539: $? = 0 configure:19542: test -s conftest.o

A clean build of revisions 12 or 13 of llvm-gcc4 produces: make[1]: *** No rule to make target `llvm-backend.c', needed by `llvm-backend.o'. Stop. While the gcc/Makefile.in has: llvm-backend.o : llvm-backend.cpp $(ALL_HEADERS) #line 2440 it also has: # APPLE LOCAL begin LLVM #line 1018 ifneq ($(LLVMOBJDIR),) OBJS-common += llvm-backend.o llvm-convert.o

The curent llvm svn (r54623) is unable to link the gfortran compiler in llvm-gcc-4.2 svn. I am getting the error... c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \

I'm attempting to build Firefox on Windows using clang-cl with -fprofile-instr-generate (*), but I'm running into some linker errors that I haven't been able to make sense of. lld-link.exe: error: duplicate symbol: __profc_?width at ios_base@std@@QEBA_JXZ in minidump-analyzer.obj and in ..\google-breakpad\src\processor\basic_code_modules.obj lld-link.exe: error: duplicate symbol:

Hi Jack, > The curent llvm svn (r54623) is unable to link the gfortran > compiler in llvm-gcc-4.2 svn. I am getting the error... ... > Undefined symbols: > "_create_init_utf16_var", referenced from: > _darwin_build_constant_cfstring in libbackend.a(darwin.o) this is probably due to recent Apple changes. Fortran builds on linux. > Why is c++ being used

Hello, Jeff. You wrote Saturday, January 22, 2005, 3:57:28 AM: JC> Reid, the binary/text mode is a valid issue. This set of flags worked for me: std::ios_base::out | std::ios_base::trunc | std::ios_base::binary Yes, there are open issues with std::ios_base::binary, but llvm are not affected with them now. JC> I have successfully used a bytecode file on Windows that was created JC> on

I've read that LLVM can convert from C++ to C code. So I've used it in such a way: I'm Windows-user so I used MinGW. I employed this file as the test: llvm-hello.cpp: #include <iostream> int main(int argc, char* argv[]) { system("pause"); return 0; } result of "llvm-g++ C:\llvm_hello.cpp -o C:\llvm_hellopp.exe" worked just fine. as a result of