search for: buildit

...sing llvm-gcc4 as a drop-in to Apple's gcc to build multi- > architecture binaries. Leo, don't feel bad. The process to get an "apple-style" build working takes a liberal amount of black magic. Devang, Bill, Dale, do you guys happen to know how to run build_gcc without the buildit script driving it? -Chris -- http://nondot.org/sabre/ http://llvm.org/

Currently, to get LLVM to build "Apple-style," it's necessary to copy two files (utils/buildit/GNUmakefile and utils/buildit/build_llvm) into the top-level directory. This is generally a PITA inside of Apple. (I'll spare you the gory details. :-) I'd like to fix this for Apple, and I want to avoid compromising anybody else's build system. I've never used CMAKE, so...

Thanks for the hint, Devang. On Jul 6, 2007, at 7:26 PM, Devang Patel wrote: > You need to build darwin driver to use -arch. Try using build_gcc > script to configure and build llvm-gcc. Well, I guess this task exceeds my expertise. I just thought there was some obvious mistake I made because a lot of people might be using llvm-gcc4 as a drop-in to Apple's gcc to build multi-

On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: > Currently, to get LLVM to build "Apple-style," it's necessary to > copy two files (utils/buildit/GNUmakefile and utils/buildit/ > build_llvm) into the top-level directory. Why not: $ RC_ARCHS="x86" make echo Apple Build. Apple Build. $ make echo Standard Build Standard Build $ cat Makefile ifneq ($(RC_ARCHS),) include Makefile.apple else all: echo Standard Build endif mrs $ ca...

On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >> Currently, to get LLVM to build "Apple-style," it's necessary to >> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >> build_llvm) into the top-level directory. > > Why not: > > $ RC_ARCHS="x86" make > echo Apple Build. > Apple Build. > $ make > echo Standard Build > Standard Build > $ cat Makefile > ifneq ($(RC_ARCHS),) > includ...

...#39;s gcc to build multi- >> architecture binaries. > > Leo, don't feel bad. The process to get an "apple-style" build > working > takes a liberal amount of black magic. > > Devang, Bill, Dale, do you guys happen to know how to run build_gcc > without the buildit script driving it? > No. I never looked at the buildit script. There be dragons there! The build_gcc script could be scoured to look for how it uses the - arch stuff. From what I've seen as the build goes by on the screen, it builds llvm-gcc 4 times and then applies some magic afterwards...

...Oct 9, 2009, at 8:40 AM, Stuart Hastings wrote: > > On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > >> On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >>> Currently, to get LLVM to build "Apple-style," it's necessary to >>> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >>> build_llvm) into the top-level directory. >> >> Why not: >> >> $ RC_ARCHS="x86" make >> echo Apple Build. >> Apple Build. >> $ make >> echo Standard Build >> Standard Build >> $ cat Ma...

Since the original buildit script doesn't cover my needs I switched to a custom but really similar script, in the meantime I also got the habit to dig for new flags and support and the __GLIBCXX__ define was hiding some of this errors. I see that other linux-based operating system offer this kind of support and they ev...

...uart Hastings wrote: > >> >> On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: >> >>> On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >>>> Currently, to get LLVM to build "Apple-style," it's necessary to >>>> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >>>> build_llvm) into the top-level directory. >>> >>> Why not: >>> >>> $ RC_ARCHS="x86" make >>> echo Apple Build. >>> Apple Build. >>> $ make >>> echo Standard Build >&...

...ing libc++, but I’m not aware of what the specific issues were (hence the ?). >> >> -Chris > > +kledzik and bogner, who looked into this last. Duncan was concerned about libc++ on darwin. The problem was/is that the shipping Apple libc++.dylib did not use CMake (or the previous buildit script). It used its own Xcode project which passed a bunch of special linker flags. Building libc++ for darwin without the special flags produced a dylib that only partially worked. I have not recently tried to build libc++ for darwin from the LLVM repository. So, I don’t know if anyone has upd...

The following web say the libc++abi is ready on arm.http://libcxxabi.llvm.org/spec.html I try to build libc++ and libc++abi for host x86_64(linux) and target arm(linux) but fail.I have read the web http://llvm.org/docs/HowToCrossCompileLLVM.html Does anyone know whether it's available for my need? If you know how to build, what is the build options you use? Best regards cschen --------------

...wants to look at DESCRIPTION, so i've let that also come into the package tarball. however, when i run "R CMD check" with DESCRIPTION.in in the tree, it fails: ---- bash greg-minshalls-mbp: {3359} R CMD check image2k_0.1.tar.gz * using log directory ?/Users/minshall/src/mine/image2k/buildit/image2k.Rcheck? * using R version 3.0.3 (2014-03-06) * using platform: x86_64-apple-darwin13.1.0 (64-bit) * using session charset: UTF-8 Error in if (desc["Priority"] == "base") { : missing value where TRUE/FALSE needed Execution halted ---- (whereas if i remove DESCRIPTION....

...arm(linux) but fail. >> > > Failing in what way? If this isn't working out of the box, we've done > something wrong. Yeah, it would help to know more specifics about where you're getting stuck. > > jroelofs might know more... For my baremetal arm toolchain, I use buildit&testit for libc++abi, and buildit&lit for libc++... Which is a bit different than what you'll get out of using cmake for it. Also, I've customized both buildits, the testit, and libc++'s lit config file to do this, and those changes are very specific to my environment (I don'...

Hello: ..I met a problem when I run buildit c++ standard It tells me Fatal error miss head file "string.h". I cannot found the file in include files...on svn sever..Thanks for read my e-mail..and Sorry about my poor English. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pi...

Hi to all, when I download the clang/llvm officila binaries, I found the libc++ headers under lib directory, but I didn't found libc++.so. Why you ship libc++ headers but no shared library? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131212/36204500/attachment.html>

> On Feb 3, 2015, at 1:06 PM, Jonathan Roelofs <jroelofs.lists at gmail.com> wrote: > > > > On 2/3/15 12:08 PM, Chris Bieneman wrote: > >> Other issues not tracked by bugs: >> >> * CMake builds for libc++? > Can you elaborate... what do you mean by this? AFAIK this already works. Duncan made a comment on IRC about being libc++, but I’m not aware

Hi, I'm under Ubuntu 13.10 amd64 I just compiled both my libcxx and my libcxxabi. I noticed this really weird behaviour, while trying to compile some C++11-compliant piece of code I get this error at runtime exception_ptr not yet implemented Aborted (core dumped) Now my experience tells me that this is something that can easily be related to the ABI, so I go to the official libcxxabi

So my original post subject was for -march, but that was my mistake. The command line option is -arch. Since presumably Macports is just fetching an llvm tar ball from some repository, is the issue that llvm has been misconfigure in some obvious way? Yes, I can take a look at the driverdriver.c source file as well. Should this also be working in LLVM 2.9 or is the latest SVN also needed? On

...t; Failing in what way? If this isn't working out of the box, we've done > > something wrong. > Yeah, it would help to know more specifics about where you're getting > stuck. > > > > > jroelofs might know more... > > For my baremetal arm toolchain, I use buildit&testit for libc++abi, and > buildit&lit for libc++... Which is a bit different than what you'll get > out of > using cmake for it. Also, I've customized both buildits, the testit, and > libc++'s lit config file to do this, and those changes are very specific > to...

Hello all, I have replaced the llvm-gcc shipped with the Xcode by the latest version and I was wondering if I have missed something... (everything *seems* to work). Here's what I did: 0. Checkout LLVM (and clang) + llvm-gcc 1. Build LLVM (with clang) and install into /Developer/usr/local : # mkdir llvmobj # cd llvmobj # CC=gcc-4.2 CXX=g++-4.2 ../llvm/configure