[Buildroot] [PATCH 1/1] postgresql: remove devfiles from target

Floris Bos bos at je-eigen-domein.nl
Wed Aug 13 10:53:41 UTC 2014


On 08/13/2014 09:26 AM, Thomas Petazzoni wrote:
> On Tue, 12 Aug 2014 19:39:20 +0200, Floris Bos wrote:
>
>>> More precisely: it will simply not work. The <pkg>_CONFIG_SCRIPTS
>>> mechanism assumes that the <pkg>-config files are shell scripts, in a
>>> certain format. With an ELF executable compiled for the target:
>>>
>>>    1/ There's no way the <pkg>_CONFIG_SCRIPTS mechanism can work
>>>
>>>    2/ There's no real point in keeping this file on the build machine,
>>>       because it's an executable built for the target.
>> Do wonder if we shouldn't provide a simple replacement script for
>> pg_config, e.g. just implementing "--includedir" and "--libdir"
>> Might be less work than patching configure scripts that want to call
>> pg_config.
> Yes, that's certainly an option. If there are many packages relying on
> pg_config, it's going to be easier to provide a fake pg_config rather
> than patching all those packages (such as PHP). Maybe even this
> approach could be submitted for upstream inclusion in Postgresql?

Convincing upstream to go back to a shell based pg_config might be 
difficult.
They actually had that at some point, but replaced it with the current 
application, because they needed a solution that also works on Windows 
(natively, without using Mingw/cygwin)

-- 
Yours sincerely,

Floris Bos




More information about the buildroot mailing list