| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | <jd(at)commandprompt(dot)com> |
| Cc: | <peter_e(at)gmx(dot)net>, <alvherre(at)commandprompt(dot)com>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/php in pg_pltemplate |
| Date: | 2005-11-26 15:55:27 |
| Message-ID: | 1262.69.245.167.107.1133020527.squirrel@www.dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake said:
>
>> The build order would be:
>>
>> 1. postgresql
>> 2. php
>> 3. plphp
>>
>> There is not circular build dependency there.
>
> Not only that, plphp does not require the building of php. It can link
> directly to the .so file :)
>
This makes no sense. Where do you get the .so file and the headers you will
undoubtedly also need?
Also, having to put php in the middle of this sequence is ugly, to say the
least.
I'll be curious to see how we are going to have to manage a build system
like this with buildfarm - it sounds like it will make life more
complicated, but maybe it will work. Certainly it will make us have to use
more conditional logic.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2005-11-26 16:12:15 | Re: SHOW ALL output too wide |
| Previous Message | Alvaro Herrera | 2005-11-26 15:41:41 | Re: PL/php in pg_pltemplate |