Re: flex/bison output wrongly created in the source directory - Mailing list pgsql-hackers

From Warren Turkal
Subject Re: flex/bison output wrongly created in the source directory
Date
Msg-id 7fdf8c4d0801092330v6364028l9a9c08e2f6b595bb@mail.gmail.com
Whole thread Raw
In response to Re: flex/bison output wrongly created in the source directory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jan 9, 2008 9:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "Warren Turkal" <wturkal@gmail.com> writes:
> > I was wondering if there is a reason that the flex and bison and other
> > generated source files end up in the source directory when doing an
> > out-of-tree build. Would a patch that puts those files in the build
> > trees be accepted?
>
> Probably not, since our intention is that those files be distributed as
> part of source tarballs.

That makes sense.

> Also, since they are (or should be) architecture-independent, what's the
> point?  Out-of-tree builds are intended to support building for multiple
> architectures in parallel; but there's no reason to force independent
> reconstructions of these common derived files.

I was not building multiple builds in parallel as I thought they might
get fouled by the different builds. Since they do appear to not
change, I think they are just fine. Thanks for the help!

wt


pgsql-hackers by date:

Previous
From: "Warren Turkal"
Date:
Subject: Re: operator suggest " interval / interval = numeric"
Next
From: "Gokulakannan Somasundaram"
Date:
Subject: Re: Some ideas about Vacuum