Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Floris Bos <bos@je-eigen-domein.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] postgresql: remove devfiles from target
Date: Wed, 13 Aug 2014 12:53:41 +0200	[thread overview]
Message-ID: <53EB43B5.2050402@je-eigen-domein.nl> (raw)
In-Reply-To: <20140813092654.54197f53@free-electrons.com>

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

      reply	other threads:[~2014-08-13 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 17:34 [Buildroot] [PATCH 1/1] postgresql: remove devfiles from target Floris Bos
2014-08-10  7:01 ` Thomas De Schampheleire
2014-08-10 10:55   ` Floris Bos
2014-08-10 12:54     ` Thomas De Schampheleire
2014-08-12 16:50       ` Thomas Petazzoni
2014-08-12 17:39         ` Floris Bos
2014-08-13  7:26           ` Thomas Petazzoni
2014-08-13 10:53             ` Floris Bos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53EB43B5.2050402@je-eigen-domein.nl \
    --to=bos@je-eigen-domein.nl \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox