search for: erickt

...;m compiling llvm with: $ CXX='g++ -m32' CC='gcc -m32' CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32 ./configure --disable-bindings --{build,host,target}=i686-apple-darwin --enable-targets=x86,x86_64,cbe --enable-optimized $ make $ make install It will eventually error out with: /Users/erickt/Projects/llvm/gcc-i386/llvm-build-Release/Release+Asserts/bin/clang -no-integrated-as -ccc-install-dir /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/ -arch armv6 -fvisibility=hidden -DVISIBILITY_HIDDEN -mkernel -DKERNEL_USE -Wall -Werror -O3 -fomit-frame-pointer -miphoneos-version-min=1....

...in your build directory, and run "make" there. Anyway, I think the problem you're probably running into is that you need to link with the ocaml "-cc g++" argument in order to link against the c++ libraries, as in this: /opt/local/bin/ocamlopt -cc g++ -pp camlp4of -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/Release+Asserts/lib/ocaml llvm.cmxa llvm_analysis.cmxa llvm_executionengine.cmxa llvm_target.cmxa llvm_scalar_opts.cmxa -o /Users/erickt/Projects/llvm/gcc/...

Chris Lattner wrote: > Patches welcome. Please send a patch, or even just some suggested > text, and we'll be happy to include it. Remember that the people who > usually end up writing the FAQ's already know all the answers, so it's > hard for us to see things from fresh perspectives sometimes :) > > -Chris > Actually, my request for more info in the

lcs for language compiling system? It's a suggestive of the old name, easy to remember, easy to say, and seems to be easy to google. Advanced could be prepended to it to make it alcs to make it even more unique. -e

...s designed to be used for cross compiling, configuration, and being really simple to extend, since it's written in python (3.0b2). It's also only ~3500 lines, which is way smaller than any other build system I've seen for what it supports. I'll be on #llvm and #felix on freenode (as erickt) if anyone actually wants to talk about it.

Erick Tryzelaar wrote: > Actually, my request for more info in the "Getting Started" had some > hidden questions, as I don't know the answer to them :) So to be a > little more clear, here are the two I had: > > Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 > frontends uses? > > Is it possible to install both the gcc4 and

Kenneth Boyd <zaimoni at zaimoni.com> writes: > I'm indulging in this exercise to enable testing a native MingW32 build > of LLVM in Windows. If LLVM's DejaGNU usage is the same as GCC's, I'll google or ask on the MinGW mailing list how MinGW testers run the GCC testsuite, before trying to fix something that maybe is not broken. > There are more portability

Hi Everyone, LLVM is a growing project, and many of us are very fond of it. :) LLVM is continuing to grow, both in maturity in specific areas and in scope of areas that it is applicable to. When we first started the project, we focused on the design of the intermediate representation. It is a strong design goal that the IR be a self-contained virtual instruction set, which fully describes

I've run into a situation where we'd like to replace rcp with rsync, but we've run into a difference in interface, which is causing us problems. Here's the problem. If we run this in rsync: > mkdir tmpdir; cd tmpdir > mkdir a; touch a/b > rsync -r a b/ > ls b a/ But for all the other programs, we get something different: > cp -r a c/ > ls c foo > cp

Scott Michel wrote: > That part about "native" -- yeah, it's there. The existence predicate > returns true. IT'S SOMETHING THAT IS EASILY SKIPPED OVER WHEN SKIMMING > THE DOCUMENT BECAUSE, HECK, THE GCC3 DRIVER COMPILES DIRECTLY TO > BYTECODE SO WHY DOESNT GCC4? > > It's a "least surprise" issue. If gcc3 produces bytecode directly, why > did the

Reid Spencer wrote: > Yes. Could you please file a bug report for this so we don't forget > about it. I would really appreciate it. > Will do. >> So does that mean that if we're doing a pure llvm, or llvm + llvm-gcc4, >> we can just do "make" and not "make tools-only"? >> > > Yes. The makefile detects llvm-gcc4 and skips the

llvm-gcc4 currently references some files from the build directory of llvm, but looking through the make file, I haven't yet come across a file that llvm-gcc4 needs that isn't installed with llvm. I checked, and all the headers for the src and obj are installed into ${prefix}/include/llvm and ${prefix}/include/llvm-c. All the main object files are the same as well. The only difference

Tanya Lattner wrote: > You can set the program-prefix to be "llvm-". We actually recommend > this and its in the README.llvm. We do not require it though. > > -Tanya > Hello Tanya. Yes, I'm aware of this, but one of the programs that got installed for me, like i686-apple-darwin8.10.1-gcc-4.0.1, was not getting the program prefix, and was getting used by gcc.

I've got ocaml installed in a non-standard location, and while the svn version of llvm seems to detect my ocaml binaries, it doesn't seem add "ocamlc -where" to the c include search path. This causes bindings/ocaml/llvm/llvm_ocaml.c to error out unless I run "make CFLAGS=`ocamlc -where`". Any chance that this could be added?

Hello! I'm having some problem compiling llvm 2.1 for macports. I'm getting errors from some undefined symbols. What am I doing wrong? I couldn't find anything on the website or the mailing list. Thanks. > cd "/opt/local/var/macports/build/_Users_Shared_erickt_Projects_macports-trunk_dports_lang_llvm/work/build" && ../llvm-2.1/configure --enable-optimized --prefix=/opt/local ... > make tools-only ... llvm[2]: Linking Release executable opt (without symbols) /usr/bin/ld: warning prebinding disabled because of undefined symbols /usr/bin/l...

Hello again, I'm exploring llvm's intermediary representation with this code: //////////////////////////////////// %.LC0 = internal constant [13 x sbyte] c"hello world\0A\00" declare int %puts(sbyte*) implementation int %main() { %cast210 = getelementptr [13 x sbyte]* %.LC0, long 0, long 0; call int %puts(sbyte* %cast210) ret int 0 }

Tanya Lattner wrote: > LLVMers, > > The 2.1 pre-release (version 1) is available for testing: > http://llvm.org/prereleases/2.1/version1/ A couple months ago, I had a problem packaging llvm-gcc for macports because one of the binaries from llvm-gcc was somehow getting used by Apple's gcc driver instead of the native one. This was causing some subtle bugs for people. Anyway,

Hello, It looks like the "Getting Started" is missing some info about the gcc 4.0 frontend. Since it doesn't follow the setup of the cfrontend/gcc3.4 package, a couple sections describing the front end don't cover the gcc4 package. Here are the couple things I'd wish could be fleshed out a bit more: Under "Getting Started Quickly (A Summary)", it'd be nice

Hello, I've put together a macports version of llvm and llvm-gcc4, but I've run into a problem with how gcc on the mac works. llvm-gcc4 creates an executable named: /opt/local/bin/powerpc-apple-darwin8-gcc-4.0.1 Which happens to be the same executable in /usr/bin. Because I have /opt/local before /usr/bin, gcc ends up using llvm-gcc4 to build all my code. Most of the time this

Reid Spencer wrote: > Yes, but its a bit verbose. The variables that control this are all > defined in the Makefile.config file. The variables are: > > PROJ_prefix := /proj/llvm/install-1 > PROJ_bindir := /proj/llvm/install-1/bin > PROJ_libdir := /proj/llvm/install-1/lib > PROJ_datadir := /proj/llvm/install-1/share > PROJ_docsdir :=