From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] postgresql: add host-zic dependency
Date: Tue, 22 Apr 2014 20:21:39 +0200 [thread overview]
Message-ID: <20140422202139.1830d8b8@skate> (raw)
In-Reply-To: <20140422164108.GA3601@free.fr>
Dear Yann E. MORIN,
On Tue, 22 Apr 2014 18:41:08 +0200, Yann E. MORIN wrote:
> host-zin only builds the 'zic' program, which pacakge can access using
> $(ZIC), so host-zip (our package) does not need the tz-data itslef.
Right.
>
> But postgresql needs the time zone info. It can use either the system
> ones, or it has a limited set bundled in its source tree, in:
> postgresql-9.3.3/src/timezone/data/
What I'm worried about here is *precisely* that even though we build
our own host-zic, it might end up time zone infos from the host system.
And nowhere we check that these are available/sane/etc.
So I think we should either (1) ensure that PostgreSQL only uses its
one limited set of time zone data when --with-system-data is *not*
passed, or (2) always build with tzdata.
> That's what the error message hints at:
>
> When cross-compiling, either use the option --with-system-tzdata to use
> existing time-zone data, or set the environment variable ZIC to a zic
> program to use during the build.
Yes, I've read this error message. But I'm worried that just pointing
ZIC to a zic program is papering over the fact that we in this case
rely on the time zone info from the host system.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-22 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 15:41 [Buildroot] [PATCH 1/1] postgresql: add host-zic dependency Peter Seiderer
2014-04-22 15:52 ` Thomas Petazzoni
2014-04-22 16:41 ` Yann E. MORIN
2014-04-22 18:21 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-22 19:11 Peter Seiderer
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=20140422202139.1830d8b8@skate \
--to=thomas.petazzoni@free-electrons.com \
--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