From owner-freebsd-current@FreeBSD.ORG Sun Jun 14 18:22:04 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 190FD10656C3 for ; Sun, 14 Jun 2009 18:22:04 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id A2E648FC14 for ; Sun, 14 Jun 2009 18:22:03 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 9F5551CC2E; Sun, 14 Jun 2009 20:22:02 +0200 (CEST) Date: Sun, 14 Jun 2009 20:22:02 +0200 From: Ed Schouten To: Chuck Robey Message-ID: <20090614182202.GN48776@hoeg.nl> References: <20090604093831.GE48776@hoeg.nl> <20090608.120552.756910862.imp@bsdimp.com> <4A353D49.1050202@telenix.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="srAoGIOs8asUHz4E" Content-Disposition: inline In-Reply-To: <4A353D49.1050202@telenix.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: current@freebsd.org, "M. Warner Losh" Subject: Re: Clang: now available from a SVN server near you! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2009 18:22:04 -0000 --srAoGIOs8asUHz4E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Chuck, * Chuck Robey wrote: > I feel a bit like an idiot needing to ask this, but I downloaded the stuf= f on > llvm/clang, but I don't know the name of the directories, and I need to a= sk some > items. (Before someone kindly points this out, I've been running -current > fairly regularly since 1.0, and I'm completely aware that running current= is > very nearly completely a "run at your own risk" thing. I have a pretty g= ood > track record and being able to fix things, and I accept this risk just li= ke the > earlier ones). So, I need the next very few questions to help me on my w= ay: You're not being an idiot; it's something that I should mention somewhere anyway. > First is the complete set of llvm/clang code in that new src/cddl subdire= ctory? > I looked really hard for directories named either clang or llvm, and si= nce I > didn't find anything, is there anything like a README that explains what's > sitting where? I mean, stuff like what's in the currently available src/= README, > but in a little additional detail for the new llvm/clang stuff. This is = likely > stuff that others might be curious about also, those who didn't konw any = more > about llvm than I do. Because Clang could be integrated into the LLVM repository somewhere in the very far future, I just followed the existing practice of storing the Clang source tree inside the LLVM source directory. This is also done when building llvm-devel from Ports. Sources are stored at: contrib/llvm contrib/llvm/tools/clang Both source trees contain some small modifications, mainly related to changing the compiler's default include paths. The Makefiles I wrote are all stored in: usr.bin/clang Because LLVM and Clang consists of a lot of libraries, there is a lib/ subdirectory. I initially placed this directory at lib/clang, but the problem then is that the lib32 build on amd64 will also build the Clang libraries for nothing. I'm not entirely happy with the pathnames yet, but I think it's reasonable to work with. > Is the rest of the stuff I downloaded, the rest of that tree, being kept = up to > date with the rest of the FreeBSD-current's HEAD? Or, is that being held= for > llvm testing? BTW, my insurance method here is to have a complete prebui= lt > -current tree (with gcc built and ready to be installed) sitting on the s= ide, so > if suddenly llvm won't operate, I only need to install from that other tr= ee to > get me a good gcc again. Not that I'm expecting any code problem, but I = could > cause myself some local problem, possibly, I want to protect myself from > anything. I'm honestly mostly worried about the stiching up of the new l= lvm > code with the rest of the tree, or if that needs something extra (beyond = merely > getting llvm working)? Now that there are other people who are starting to use the clangbsd branch for tests (for example Erwin's port builds), I integrate the FreeBSD, LLVM and Clang source once or twice a week. Before I commit, I usually run two buildworlds on an amd64 box, to make sure the system is at least capable of bootstrapping itself. Being able to do that still doesn't bring a lot of guarantees, but at least makes it less likely for you to completely hose your system. --=20 Ed Schouten WWW: http://80386.nl/ --srAoGIOs8asUHz4E Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAko1P8oACgkQ52SDGA2eCwU9agCeLnF7KZ+hfdKKPCtxab2022dK XwIAnA2l1RUD87mS3KyyqhHbPXb5g6wB =cND1 -----END PGP SIGNATURE----- --srAoGIOs8asUHz4E--