Re: make release broken
On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen wrote: > On 5/18/2010 2:34 AM, jhell wrote: >> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer >> wrote: make release is broken on current. Seems to be related to the lzma import. This is on i386: cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): In function `archive_compressor_xz_init': : undefined reference to `lzma_lzma_preset' ... >> >> This URL looks to be the problem you are seeing above. >> >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current >> > > make release is still broken on amd64 as of svn 208373 (2010-05-21 > 04:52:49 -0500) > > That patch seems unrelated? > That patch is unrelated - it is for building current on RELENG_7 or something like that. What needs done is /src/release/$ARCH/boot_crunch.conf files need the relevant libraries added to the libs section. I haven't tested it, but I think adding -llzma there will fix the problems. -- Rob Farmer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: make release broken
On 5/18/2010 2:34 AM, jhell wrote: > On Mon, May 17, 2010 at 10:35 PM, Rob Farmer > wrote: >>> make release is broken on current. Seems to be related to the lzma >>> import. This is on i386: >>> >>> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo >>> test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo >>> newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo >>> sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd >>> -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf >>> -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail >>> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): >>> In function `archive_compressor_xz_init': >>> : undefined reference to `lzma_lzma_preset' >>> ... > > This URL looks to be the problem you are seeing above. > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current > make release is still broken on amd64 as of svn 208373 (2010-05-21 04:52:49 -0500) That patch seems unrelated? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: clangBSD build error
On Sat, May 22, 2010 at 10:26:57AM +0200, Roman Divacky wrote: > On Fri, May 21, 2010 at 07:34:22PM -0700, ambrosehuang ambrose wrote: > > 2010/5/21 Roman Divacky > > > > > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > > > I found my clang version is : > > > > [r...@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 > > pes ~/clangbsd$ md5 lib/libc/stdlib/malloc.c > MD5 (lib/libc/stdlib/malloc.c) = 312d85c5cf51aa3fa1ef46c0832f0056 > > can you compare to your malloc.c ? and if it differs can you send me > your malloc.c ? I just tried with llvm-devel port and malloc.c from clangbsd and it works just ok. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: clangBSD build error
On Fri, May 21, 2010 at 07:34:22PM -0700, ambrosehuang ambrose wrote: > 2010/5/21 Roman Divacky > > > On Thu, May 20, 2010 at 10:10:23PM +0800, ambrosehuang ambrose wrote: > > > I found my clang version is : > > > [r...@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 pes ~/clangbsd$ md5 lib/libc/stdlib/malloc.c MD5 (lib/libc/stdlib/malloc.c) = 312d85c5cf51aa3fa1ef46c0832f0056 can you compare to your malloc.c ? and if it differs can you send me your malloc.c ? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"