From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/icu: bump version to 60.1
Date: Mon, 04 Dec 2017 08:20:25 +0100 [thread overview]
Message-ID: <pi9ffex2o8.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20171203210012.0cb2bc4c@windsurf.home
Hi Thomas,
Am Sun, 03 Dec 2017 21:00:12 +0100 schrieb Thomas Petazzoni:
> Curious: how many packages that depend on ICU did you build? From past
> experience, each major ICU bump very often causes a number of build
> failures in other packages.
this defconfig builds fine:
BR2_x86_64=y
BR2_x86_core2=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/
tarballs/br-x86-64-core2-full-2017.05-1078-g95b1dae.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_6=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_4=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_PACKAGE_MPD=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_DRI_DRIVER_I965=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_XORG7=y
BR2_PACKAGE_NODEJS=y
BR2_PACKAGE_PHP=y
BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_PYICU=y
BR2_PACKAGE_HARFBUZZ=y
BR2_PACKAGE_RAPTOR=y
BR2_PACKAGE_XERCES=y
BR2_PACKAGE_CPPCMS=y
BR2_PACKAGE_CPPCMS_ICU=y
BR2_PACKAGE_DOVECOT=y
BR2_PACKAGE_ZNC=y
> What are the changes between 59.1 and 60.1 ? Anything significant that
> has a chance of breaking packages that depend on ICU ?
The release notes can be found here:
http://site.icu-project.org/download/60
and, afaics, they do not include a hint for breaking changes.
Regards, Bernd
next prev parent reply other threads:[~2017-12-04 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 19:41 [Buildroot] [PATCH 1/1] package/icu: bump version to 60.1 Bernd Kuhls
2017-12-03 20:00 ` Thomas Petazzoni
2017-12-03 22:01 ` Mario Lang
2017-12-04 7:20 ` Bernd Kuhls [this message]
2017-12-04 10:33 ` Thomas Petazzoni
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=pi9ffex2o8.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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