search for: vpath

Hi: I've been seeing intermittent build failures with the extlinux target, and I believe I've tracked it down to a VPATH issue. See this make -d log: Finished prerequisites of target file `extlinux'. Prerequisite `extlinux.o' is newer than target `extlinux'. Prerequisite `setadv.o' is newer than target `extlinux'. Prerequisite `extlinux_bss_bin.o' is newer than target `e...

On Dec 30, 2008, at 2:54 PM, Talin wrote: > OK changes made and new patch attached. Nice +++ utils/unittest/Makefile (revision 0) ... +# This has to come after Makefile.common, since it doesn't allow us to +# override the VPATH value unless we set PROJECT_NAME, which we don't want +# to do. +VPATH = $(LLVM_SRC_ROOT)/utils/unittest/googletest/src/ Why play with VPATH here? What is this doing? Can this be handled a different way? Similarly in makefile.unittest. +++ unittests/ADT/DenseMapTest.cpp (revision 0) +...

Hello, c/s 17138 introduced the use of VPATH instead of symlinks to access to libelf files. However, that not only provides access to .c files, but also to .o files. That means that if one compiles the hypervisor before the tools, libxenguest.a contains .o files intended to the hypervisor, containing references to printk, etc. and thus is u...

...tner <clattner at apple.com> > On Dec 30, 2008, at 2:54 PM, Talin wrote: > > OK changes made and new patch attached. > > +++ utils/unittest/Makefile (revision 0) > > ... > +# This has to come after Makefile.common, since it doesn't allow us to > +# override the VPATH value unless we set PROJECT_NAME, which we don't want > +# to do. > +VPATH = $(LLVM_SRC_ROOT)/utils/unittest/googletest/src/ > > > Why play with VPATH here? What is this doing? Can this be handled a > different way? Similarly in makefile.unittest. > Removed VPATH in thi...

I am trying to do VPATH builds of R3.1.3, i.e. binaries built outside the source directory. It works just fine on Linux but on Mac OSX (Mavericks) I get the following trace from make, after a successful configure step. Any insights gratefully received. make is GNU make 3.81 on both systems. bash-3.2$ make make make[1...

...>> passthru ("--error-exitcode=119"); >>> - passthru_format ("--suppressions=%s/valgrind-suppressions", srcdir); >>> + passthru_format ("--suppressions=%s/valgrind/suppressions", builddir); >> >> Is this still right under VPATH? > > I believe so ...? Note this is the generated/concatenated file which > is why I changed srcdir to builddir. Yes, if it's generated, then builddir should be right. But this is an independent fix, so I might have split it to another patch. (I guess I haven't got that far i...

# HG changeset patch # User Matthias Andree <matthias.andree at gmx.de> # Date 1246993296 -7200 # Branch HEAD # Node ID c884491cb1a61ef50e227fcf4bb77d2e449c1e3a # Parent dff7312629a72f6ee90ab470ad0d50dfa68e6f71 Fix VPATH build of RQUOTA support. Some rpcgen derive #include "..." paths from the infile argument. This will be off for VPATH builds, as the generated rquota_xdr.c code will look in $(srcdir), but we'll generate the rquota.h file in $(builddir). Play safe and copy rquota.x to $(builddir) fir...

The ocaml.opt compiler defaults to building things in the same directory as its input; we need explicit -o options to build in a VPATH $(builddir) when $(srcdir) is read-only (as is the case during 'make distcheck'). We also have to build any side effect files explicitly in cases where we can't directly use -o to control those outputs alongside the final product. Thanks: Richard W.M. Jones Signed-off-by: Eric Blake &l...

I was fiddling around to get VPATH builds working again, and the only nontrivial fix was for ordinals.h. Because it is auto-generated, it goes in the build directory, not the source directory, and thus requires some fiddling to get included properly. After looking at it, I don't see why it needs to be auto-generated. Rather t...

...iling manpage bugs for ksh93 to include > > changes to existing pages and new manpages for ksh93(1) and its > > builtins (builtin(1), disown(1)). > > > > CR 6457823 New manpages needed for ksh93 > > > > However, I do not see any manpages for vmap(1), alarm(1), or vpath(1). > > Are there any? nroff versions would be preferable, as this could make > > the manpage work easier. I do have nroff versions for the others. > > "vmap" and "vpath" are AFAIK for the FS3D support (3D filesystem > support) Further references for the...

# HG changeset patch # User Bastian Blank <waldi@debian.org> # Date 1201284962 -3600 # Node ID 11b2e8baa6bf93b8ec4b3b4fe0256d2ce34f2699 # Parent 31adb5c972d03e45cb746cd2305126ea2571282f Use VPATH instead of symlinks for libelf inclusion into libxenctrl. Signed-off-by: Bastian Blank <waldi@debian.org> diff -r 31adb5c972d0 -r 11b2e8baa6bf tools/libxc/Makefile --- a/tools/libxc/Makefile Thu Jan 24 14:41:26 2008 +0000 +++ b/tools/libxc/Makefile Fri Jan 25 19:16:02 2008 +0100 @@ -31,20 +...

...git snapshot under Debian Wheezy gives me: configure.ac:7: option `info-in-builddir' not recognized autoreconf: automake failed with exit status: 1 Do I now need a specific newer version of automake? Seems to be the result of commit 13f9bc1ff199bea46 "Add support for out-of-tree ("VPATH") builds." Undoing the change to configure.ac fixes the compile for me. (Though 'make check' fails in the invite-join.test, still investigating if it is something local) c'ya sven-haegar -- Three may keep a secret, if two of them are dead. - Ben F.

I've got a tough to track down problem that seems to be samba related. I've got a directory structure like this: topdir/ lib1/src lib1/include lib2/src lib2/include etc. Each src directory has a makefile in it. VPATH is set to ../include. I'm running cygwin bash and make. In some directories, make can't find files in ../include. In other directories, make finds everything fine. The same makefiles work fine (i.e. make finds include files in all directories) when I run them on both a linux and solaris...

...als, as that's not a true leak? > passthru ("--error-exitcode=119"); > - passthru_format ("--suppressions=%s/valgrind-suppressions", srcdir); > + passthru_format ("--suppressions=%s/valgrind/suppressions", builddir); Is this still right under VPATH? > passthru ("--trace-children=no"); > passthru ("--run-libc-freeres=no"); > passthru ("--num-callers=20"); > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org

I have 6 zfs pools and after rebooting init 6 the vpath device path names have changed for some unknown reason. But I can''t detach, remove and reattach to the new device names....ANY HELP! please pjde43m01 - - - - FAULTED - pjde43m02 - - - - FAULTED - pjde43m03 - - - - FAULTED -...

...>> On Dec 30, 2008, at 2:54 PM, Talin wrote: >> >> OK changes made and new patch attached. >> >> +++ utils/unittest/Makefile (revision 0) >> >> ... >> +# This has to come after Makefile.common, since it doesn't allow us to >> +# override the VPATH value unless we set PROJECT_NAME, which we don't want >> +# to do. >> +VPATH = $(LLVM_SRC_ROOT)/utils/unittest/googletest/src/ >> >> >> Why play with VPATH here? What is this doing? Can this be handled a >> different way? Similarly in makefile.unittest. &g...

Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like powerpath, MPXIO or VxDMP. Here is the error message when I try to create my pool: bash-3.00# zpool create tank /dev/dsk/vpath1a warning: device in use checking failed: No such device internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c bash-3.00# zpool create tank /dev/dsk/vpath1c cannot open ''/dev/dsk/vpath1c'': I/O error bash-3.00# zpool create tank vpath1 cannot open ''v...

...me care! .PHONY: uninstall --- x/buildconfigs/Rules.mk +++ x/buildconfigs/Rules.mk @@ -22,32 +22,58 @@ LINUX_SERIES ?= 2.6 LINUX_VER ?= $(shell grep "^LINUX_VER" buildconfigs/mk.linux-2.6-xen | sed -e ''s/.*=[ ]*//'') # Setup Linux search path -LINUX_SRC_PATH ?= .:.. -vpath linux-%.tar.bz2 $(LINUX_SRC_PATH) -vpath patch-%.bz2 $(LINUX_SRC_PATH) +vpath linux-%.tar.bz2 $(DOWNLOAD_PATH) +vpath patch-%.bz2 $(DOWNLOAD_PATH) # download a pristine Linux kernel tarball if there isn''t one in LINUX_SRC_PATH +ifndef LINUX_REPO_KERNEL_PATH linux-%.tar.bz2: override _L...

...ual sources, so either > adding a new source to any POTFILES or changing any of the listed > sources in any POTFILES will trigger a new pot rebuild. Right, so I believe the first version (posted above) is correct, because $(srcdir)/.. is not necessary (because automake is supposed to add a VPATH for these builds). Which apparently are called "VPATH builds", not separate compilation. If you agree, I will push the first version of the 2/3 patch. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without nee...

To whom it may concern: here are the diffs which I required to make the mentioned Makefile work. I maintain several platforms of samba servers, and thus use the VPATH option in the Makefile. I've been fixing installscripts.sh as well, so that `make install` works when run from my build directory. I'm assuming SAMBA v2.x will migrate to autoconf/configure and should fix these issues, but I thought someone else might find this handy. NOTES: my system pr...