Date: Fri, 21 May 2010 19:34:22 -0700 From: ambrosehuang ambrose <ambrosehua@gmail.com> To: Roman Divacky <rdivacky@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: clangBSD build error Message-ID: <AANLkTikVdiSnhkjvN698EpUdd1VnkiSg0eztCgdnOknj@mail.gmail.com> In-Reply-To: <20100520195232.GA70802@freebsd.org> References: <AANLkTikxYjqM_MKT8O9YXxtNwwgeJFmoGk2UgK9bStOU@mail.gmail.com> <20100520072120.GA36958@freebsd.org> <AANLkTiniqavVCnQ_uy66dtJImVK020h4RDL2_F3EmVdC@mail.gmail.com> <20100520195232.GA70802@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/5/21 Roman Divacky <rdivacky@freebsd.org> > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > I found my clang version is : > > [root@lateaxfreebsd src]# clang --version > > clang version 2.0 (trunk) > > Target: *x86_64-portbld-freebsd8.0* > > Thread model: posix > > svn revision is r10379_1 in PORTS > > > > I think maybe you can use the llvm-devel in PORTS to reproduce this > > > > I try to update clang to the latest version with > > make BOOTSTRAP=1 _CKSUMFILES="", but it seems the patch file confilcts > with > > latest code? > > > > Could you tell me how to bypass the patching step ? > > there's no point in upgrading to newer clang. there were no change > in this.. are you sure you are compiling with llvm-devel the malloc.c > in clangbsd? not some older/newer version? > I'm sure the llvm-devel is version r10379 in freebsd-stable branch. I also found that the both clang from llvm-devel and clang built from clangBSD building /usr/src.svn/src/lib/libc/stdlib/malloc.c(/usr/src.svn/src is the clangBSD directory in my box) failed with same error. maybe the version of clang in llvm-devel is too low, but the clang in clangBSD itself should be OK
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikVdiSnhkjvN698EpUdd1VnkiSg0eztCgdnOknj>