search for: buildir

...th: ''make CONFIG_DEBUG_SECTION_MISMATCH=y''   GEN     .version   CHK     include/linux/compile.h   UPD     include/linux/compile.h   CC      init/version.o   LD      init/built-in.o   LD      .tmp_vmlinux1 arch/x86/kernel/built-in.o: In function `timer_interrupt'': /usr/src/buildir/linux-2.6.29.4/arch/x86/kernel/time_32-xen.c:465: undefined reference to `__udivdi3'' make: *** [.tmp_vmlinux1] Error 1 ---------------------------------------------------------   Installation steps:   1. Install Mercurial and Git (hg) :- # apt-get install mercurial gitk 2. Building Xen:...

...s-compilation. - Certificates for RSA keys size greater than 2048 Limitation for big RSA keys is resolved. - Regression tests with multi-language "distinguished name" in utf-8 To enable uncomment #SSH_DN_UTF8_FLAG='-utf8' in "[SOURECDIR]/tests/CA/config", go in "[BUILDIR]/" and run tests. If test certificates are created, before to run tests again with flag enabled, go in "[BUILDIR]/tests/CA/", run make clean (this will remove created test certificates), return to "[BUILDIR]/" and run tests again. On download page http://roumenpetrov.i...

...d/llvm-cvs I get error because no LLVM header can be found. If I specify --enable-llvm=/space/p2/ghost/build/llvm-cvs/install I get link errors like this: c++: /space/p2/ghost/build/llvm-cvs/install/Debug/lib/LLVMX86.o: No such file or directory So, it seems like, at the same time: 1. buildir != srcdir is not supported when building frontend 2. building the frontend against installed LLVM does not work either. I can get past the compile/link errors only after copying "include" directory from source dir to the build dir. Then, I'm faced with yet another problem, sorry! Th...

Dear all, Which options should I use when running the configure script and/or which changes should I make to Makeconf to build the binary for R-1.9.0 but using only statically linked libraries ? I need to build a binary that is portable between several different Linux (RedHat) distributions. Thanks in advance for your help, Melanie -- http://recherche-en-danger.apinc.org

On Thu, 2 Mar 2006, Vladimir Prus wrote: >>> The instructions seem to have one path wrong. It says to get: >> >> I'll put together a tarball today. That will be easier than dealing with >> a patch, and it will include a bunch of bugfixes since the previous email. > Further into process, I get this error: > In file included from

...03-02-llvm-gcc-4.tar.gz > > There's some confusion with --enable-llvm configure parameter. I've built > LLVM to a separate build dir. The source is ~ghost/Work/llvm-cvs and build > dir is /space/p2/ghost/build/llvm-cvs ... > So, it seems like, at the same time: > > 1. buildir != srcdir is not supported when building frontend > 2. building the frontend against installed LLVM does not work either. Correct. I currently only build the front-end against a built, but not installed, LLVM tree with srcdir = objdir. If you would like to tackle this problem and propose a...

Some of the libvirt XMLs for tests refer to a generated phony disk image, and so far the relative path used worked almost by chance. (For each disk, the path to it was ../test-data/etc, and since the overlay pointing to it is stored directly in $LIBGUESTFS_CACHEDIR, which is $buildir/tmp, then the relative path was resolved.) Instead, have configure place the right top-level directory in those XMLs, so the full path points to the generated disks. This fixes the tests for at least two cases: - we change the place where the temporary overlays are stored - in srcdir!=builddir bui...