From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/glibc/files/eblits/
Date: Wed, 30 Dec 2015 20:40:52 +0000 (UTC) [thread overview]
Message-ID: <1451508036.dfe748c6971a880e6110ee40e484895f0b57e512.vapier@gentoo> (raw)
commit: dfe748c6971a880e6110ee40e484895f0b57e512
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 30 18:35:48 2015 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Wed Dec 30 20:40:36 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dfe748c6
sys-libs/glibc: use new timezone-tools configure flag
sys-libs/glibc/files/eblits/src_configure.eblit | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/sys-libs/glibc/files/eblits/src_configure.eblit b/sys-libs/glibc/files/eblits/src_configure.eblit
index 954508c..99964fb 100644
--- a/sys-libs/glibc/files/eblits/src_configure.eblit
+++ b/sys-libs/glibc/files/eblits/src_configure.eblit
@@ -119,6 +119,11 @@ glibc_do_configure() {
${EXTRA_ECONF}
)
+ # We rely on sys-libs/timezone-data for timezone tools normally.
+ if version_is_at_least 2.23 ; then
+ myconf+=( $(use_enable vanilla timezone-tools) )
+ fi
+
# There is no configure option for this and we need to export it
# since the glibc build will re-run configure on itself
export libc_cv_slibdir=/$(get_libdir)
next reply other threads:[~2015-12-30 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 20:40 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-07 13:49 [gentoo-commits] repo/gentoo:master commit in: sys-libs/glibc/files/eblits/ Benda XU
2016-12-07 7:03 Mike Frysinger
2016-11-25 5:50 Mike Frysinger
2016-09-03 11:06 Michał Górny
2016-06-19 23:19 Benda XU
2016-06-06 13:28 Benda XU
2016-06-02 13:26 Benda XU
2016-06-02 8:08 Benda XU
2016-01-16 8:17 Mike Frysinger
2015-10-16 18:26 Mike Frysinger
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=1451508036.dfe748c6971a880e6110ee40e484895f0b57e512.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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