similar to: [LLVMdev] fudging the top-level Makefile

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.

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

On 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.

On Oct 9, 2009, at 12:34 PM, Mike Stump wrote: > > On 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

On Wed, 11 Jul 2007, Leo Fink 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- > architecture

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

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 Jul 10, 2007, at 10:41 PM, Chris Lattner wrote: > On Wed, 11 Jul 2007, Leo Fink 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

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

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 even use the same core components of my GNU/Linux distribution. You are

On Feb 3, 2015, at 1:40 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > >> On 2015 Feb 3, at 13:26, Chris Bieneman <beanz at apple.com> wrote: >> >> >>> 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:

On Sat, 3 Jun 2017 16:04:57 -0700 Tim Northover <t.p.northover at gmail.com> wrote: [snip] > I think you should be able to fix it by changing the > compiler-rt/lib/xray/test/CMakeLists.txt. If you find the > "add_compiler_rt_test" call and move "-lstdc++" to the end, just after > "-lrt" it should work. Thanks, Tim. I don't see "-lrt":

There are a couple of bug reports on the Debian rsync package about problems with a recipient filesystem that can't cope with all possible unix filenames. Notably filenames with question marks are a problem... I guess that people are trying to backup systems to a SMB share which presumably is then regularly backupped to tape. This basically sounds like a reasonable thing to do :-) Would

Hi; There is likely a supported way around this problem, but it wasn't immediately apparent to me. So, I created the enclosed patch to fix my problem. What I would like to do is the following: - run samba in "security = domain" - not use trusted domains, but allow people to connect from other domains - not maintain a local encrypted password file for samba, but instead use our

On Aug 22, 2011, at 3:59 PM, Bob Wilson wrote: > The -arch option is handled by Apple's "driver-driver", and the MacPorts build is probably not using that. See the driverdriver.c source file in llvm-gcc for details. > He's asking about the -march option which should work either way. Also, the driver-driver should be in the sources that they're using even still.

hi. i'm building a package using autotools. to propagate the package version number from configure.ac to DESCRIPTION, i'm using a DESCRIPTION.in file. both of these files are "shar"'d below. i need to distribute the DESCRIPTION.in file, as ./configure will need it. but, "R CMD check" wants to look at DESCRIPTION, so i've let that also come into the package

On Apr 4, 2009, at 6:17 AM, Duncan Sands wrote: > you need to use a separate objects directory and not build directly > in the llvm-gcc tree. For some reason the Apple people placed a file > GNUmakefile in the tree which "make" chooses in preference to the > Makefile > produced by configuring. Personally I would like to see GNUmakefile > deleted. My take, you can

it appears that by default some Apple configuration is assumed, since a simple make complains GNUmakefile:16: /CoreOS/Standard/Standard.make: No such file or directory We started with a subversion checkout, in case it matters. --------------------------------------------------------------------+ Thomas Plum, Plum Hall Inc, 3 Waihona Box 44610, Kamuela HI 96743 USA tplum at plumhall.com

On Saturday 04 April 2009 19:12:55 Mike Stump wrote: > On Apr 4, 2009, at 6:17 AM, Duncan Sands wrote: > > you need to use a separate objects directory and not build directly > > in the llvm-gcc tree. For some reason the Apple people placed a file > > GNUmakefile in the tree which "make" chooses in preference to the > > Makefile > > produced by

Hello I am new to LLVM and would like to cross-compile LLVM 2.9 on x86 (Ubuntu) to ARM using Code Sourcery LIte toolchain for ARM EABI (2011.03-41). This is the command I used to configure: ./configure --build=i686-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi followed by: make -C llvm.2.9 ENABLE_OPTIMIZED=0 I encountered the following errors: configure:error: