| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: VPATH builds fail |
| Date: | 2002-01-08 20:28:09 |
| Message-ID: | 8078.1010521689@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I said:
> I have to take that back: the bison outputs are rebuilt in the source
> tree, as indeed they should be. I'm now fairly confused about why
> the first build attempt failed and the second succeeded.
The difference appears to be that when bison is run in the source dir,
its output contains lines like
#line 121 "bootscanner.l"
However, when it's run during a VPATH build, its output contains lines
like
#line 121 "/home/postgres/pgsql/src/backend/bootstrap/bootscanner.l"
evidently because bison is invoked with a full path to the .y file in
this case.
There is *no* difference in the #include commands, but apparently the
#line directives affect gcc's default search path for include files.
Net result: I'm back to my original statement: VPATH builds will not
work with a source distribution tarball. Any objections to the
-I$(srcdir) trick?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-08 20:30:34 | Re: VPATH builds fail |
| Previous Message | Peter Eisentraut | 2002-01-08 20:27:31 | Re: VPATH builds fail |