| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Devrim Gündüz <devrim(at)gunduz(dot)org>, Christoph Berg <myon(at)debian(dot)org>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: submake-errcodes |
| Date: | 2018-04-12 18:07:38 |
| Message-ID: | 20180412180738.ztwjdu4gjojsqstb@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Gierth wrote:
> >>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> Tom> I'm beginning to get dissatisfied with this approach of expecting
> Tom> the topmost Make run to do the generated-headers work
>
> Is it worth exploring the idea of changing to a non-recursive style of
> makefile?
I looked onto this a while ago. It seems easily doable for the backend
code proper, modulo potential command-line length issues; but anything
involving shared libraries requires Makefile.shlib to be involved, which
seems painful to resolve. Once I realized the shlib problem, I stopped
trying, but if you find some way around that it may be worthwhile.
I'm altogether ignorant on how might we use it for the headers problem,
mind. I only tried to tackle the main executable.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-12 18:10:30 | Re: crash with sql language partition support function |
| Previous Message | Tom Lane | 2018-04-12 18:00:32 | Re: submake-errcodes |