Re: VPath Build Errors

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: VPath Build Errors
Date: 2022-04-14 01:20:11
Message-ID: Yld2yyloTMN7iorR@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 13, 2022 at 05:48:49PM -0700, David G. Johnston wrote:
> On Wed, Apr 13, 2022 at 5:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > > The attached log is result of (while in the versioned directory, a
> > sibling
> > > of the git repo)
> > > `../postgresql/configure`
> > > `make`
> > > `tree`
> >
> > The VPATH buildfarm members haven't been complaining, and I can't
> > reproduce a failure here, so I'm inclined to suspect pilot error.
> >
> > One point that's not very clearly documented is that your source
> > directory needs to be clean; no build products in it, except
> > possibly those that are included in tarballs.
> >
> >
> I'll double-check but that would explain it. I know it was not clean when
> I tried this.

Note that if you what you want is building multiple major versions at the same
time, the easiest way to do that is probably to use git worktrees [1] and
checkout multiple branches of the same repo at the same times, and then build
each one as you'd normally do.

[1] https://git-scm.com/docs/git-worktree

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-04-14 01:23:12 Re: Intermittent buildfarm failures on wrasse
Previous Message Michael Paquier 2022-04-14 01:20:04 Re: shared-memory based stats collector - v70