Re: flex/bison output wrongly created in the source directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Warren Turkal" <wturkal(at)gmail(dot)com>
Cc: "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: flex/bison output wrongly created in the source directory
Date: 2008-01-10 05:51:26
Message-ID: 25931.1199944286@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Warren Turkal" <wturkal(at)gmail(dot)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.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-10 06:00:09 Re: operator suggest " interval / interval = numeric"
Previous Message Warren Turkal 2008-01-10 05:38:31 Re: operator suggest " interval / interval = numeric"