Issue metadata
Sign in to add a comment
|
cros_setup_toolchains broken after glibc 2.27 upgrade |
||||||||||||||||||||||
Issue description
I ran update_chroot, which failed after updating glibc:
$ ./update_chroot
09:19:52: INFO: RunCommand: /bin/bash -c 'source /mnt/host/source/src/scripts/chroot_version_hooks.d/158_glibc_update'
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
09:19:54: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.33.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-prebuilt/host/amd64/amd64-host/chroot-2018.11.10.220311/packages/Packag
es /tmp/tmp4vYGfJ.tmp
Starting fast-emerge.
Building package >=sys-libs/glibc-2.27 net-libs/rpcsvc-proto on root
Calculating deps...
Deps calculated in 0m7.2s
[binary U ] sys-libs/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary N ] net-libs/rpcsvc-proto-1.3.1-r2
Pending 0/2, Fetching 2/2, [Time 09:20:03 | Elapsed 0m10.0s | Load 2.17 1.48 1.27]
Fetched net-libs/rpcsvc-proto-1.3.1-r2 in 1.64s
Fetched sys-libs/glibc-2.27-r6 in 1.94s
Started sys-libs/glibc-2.27-r6 (logged in /tmp/glibc-2.27-r6-QiQWT_)
Completed sys-libs/glibc-2.27-r6 (in 0m6.7s)
Pending 0/2, Building 1/1, [Time 09:20:12 | Elapsed 0m18.7s | Load 2.52 1.58 1.31]
Started net-libs/rpcsvc-proto-1.3.1-r2 (logged in /tmp/rpcsvc-proto-1.3.1-r2-dZ1x0j)
Completed net-libs/rpcsvc-proto-1.3.1-r2 (in 0m2.3s)
Pending 0/2, [Time 09:20:14 | Elapsed 0m20.9s | Load 2.72 1.64 1.33]
Merge complete
Done
INFO : Updating chroot
INFO : Clearing shadow utils lockfiles under /
INFO : Updating cross-compilers
09:20:20: INFO: Determining required toolchain updates...
09:20:20: INFO: Updating packages:
09:20:20: INFO: [u'cross-armv6j-cros-linux-gnueabi/glibc', u'cross-armv7a-cros-linux-gnueabi/glibc', u'cross-i686-pc-linux-gnu/glibc', u'cross-aarch64-cros-linux-gnu/glibc', u'cross-armv7a-cros-linux-gnueabihf/g
libc', u'cross-x86_64-cros-linux-gnu/glibc']
09:20:20: INFO: RunCommand: /mnt/host/source/chromite/bin/parallel_emerge --oneshot --update --getbinpkg --usepkgonly cross-armv6j-cros-linux-gnueabi/glibc cross-armv7a-cros-linux-gnueabi/glibc cross-i686-pc-lin
ux-gnu/glibc cross-aarch64-cros-linux-gnu/glibc cross-armv7a-cros-linux-gnueabihf/glibc cross-x86_64-cros-linux-gnu/glibc
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Local copy of remote index is up-to-date and will be used.
Starting fast-emerge.
Building package cross-armv6j-cros-linux-gnueabi/glibc cross-armv7a-cros-linux-gnueabi/glibc cross-i686-pc-linux-gnu/glibc cross-aarch64-cros-linux-gnu/glibc cross-armv7a-cros-linux-gnueabihf/glibc cross-x86_64
-cros-linux-gnu/glibc on root
Calculating deps...
Deps calculated in 0m4.1s
[binary U ] cross-x86_64-cros-linux-gnu/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary U ] cross-i686-pc-linux-gnu/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary U ] cross-armv7a-cros-linux-gnueabi/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary U ] cross-armv6j-cros-linux-gnueabi/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary U ] cross-aarch64-cros-linux-gnu/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
[binary U ] cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6 [2.23-r21] USE="multiarch%* -compile-locales% -doc% -headers-only%"
Pending 0/6, Fetching 6/6, [Time 09:20:26 | Elapsed 0m5.3s | Load 3.06 1.75 1.37]
Fetched cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6 in 2.04s
Started cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6 (logged in /tmp/glibc-2.27-r6-i9uR66)
Fetched cross-armv7a-cros-linux-gnueabi/glibc-2.27-r6 in 2.43s
Started cross-armv7a-cros-linux-gnueabi/glibc-2.27-r6 (logged in /tmp/glibc-2.27-r6-nC9VbC)
Fetched cross-x86_64-cros-linux-gnu/glibc-2.27-r6 in 2.82s
Started cross-x86_64-cros-linux-gnu/glibc-2.27-r6 (logged in /tmp/glibc-2.27-r6-cmlJ2d)
Fetched cross-aarch64-cros-linux-gnu/glibc-2.27-r6 in 3.10s
Started cross-aarch64-cros-linux-gnu/glibc-2.27-r6 (logged in /tmp/glibc-2.27-r6-p7xoQN)
=== Start output for job glibc-2.27-r6 (0m1.2s) ===
glibc-2.27-r6: >>> Running pre-merge checks for cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6
glibc-2.27-r6: * Checking general environment sanity.
glibc-2.27-r6: * Checking gcc for __thread support ...
[ !! ]2.27-r6:
glibc-2.27-r6:
glibc-2.27-r6: * Could not find a gcc that supports the __thread directive!
glibc-2.27-r6: * Please update your binutils/gcc and try again.
glibc-2.27-r6: * ERROR: cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6::crossdev failed (pretend phase):
glibc-2.27-r6: * No __thread support in gcc!
glibc-2.27-r6: *
glibc-2.27-r6: * Call stack:
glibc-2.27-r6: * ebuild.sh, line 133: Called pkg_pretend
glibc-2.27-r6: * environment, line 3181: Called sanity_prechecks
glibc-2.27-r6: * environment, line 3638: Called die
glibc-2.27-r6: * The specific snippet of code:
glibc-2.27-r6: * die "No __thread support in gcc!";
glibc-2.27-r6: *
glibc-2.27-r6: * If you need support, post the output of `emerge --info '=cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6::crossdev'`,
glibc-2.27-r6: * the complete build log and the output of `emerge -pqv '=cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6::crossdev'`.
glibc-2.27-r6: * The complete build log is located at '/var/log/portage/cross-armv7a-cros-linux-gnueabihf:glibc-2.27-r6:20181112-162028.log'.
glibc-2.27-r6: * For convenience, a symlink to the build log is located at '/var/tmp/portage/cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6/temp/build.log'.
glibc-2.27-r6: * The ebuild environment file is located at '/var/tmp/portage/cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6/temp/environment'.
glibc-2.27-r6: * Working directory: '/usr/lib64/python2.7/site-packages'
glibc-2.27-r6: * S: '/var/tmp/portage/cross-armv7a-cros-linux-gnueabihf/glibc-2.27-r6/work/glibc-2.27'
=== Complete: job glibc-2.27-r6 (0m1.2s) ===
And now it fails with the same errors whenever cros_setup_toolchains is run.
,
Nov 12
That didn't help, but I ran ./update_chroot --skip_toolchain_update, which upgraded these packages:
[binary U ] dev-util/toolchain-utils-0.0.1-r56::chromiumos [0.0.1-r55::chromiumos] USE="cros_host" 36 KiB
[binary U ] chromeos-base/tast-remote-tests-cros-0.0.1-r266::chromiumos [0.0.1-r265::chromiumos] USE="cros_host" 1875 KiB
[binary U ] dev-python/setuptools-36.7.2-r1::portage-stable [36.7.2::portage-stable] USE="{-test}" PYTHON_TARGETS="python2_7 python3_4 -pypy -pypy3 -python3_5 -python3_6" 1536 KiB
[binary U ] chromeos-base/chromeos-config-host-0.0.1-r351::chromiumos [0.0.1-r350::chromiumos] USE="cros_host" PYTHON_TARGETS="python2_7" 166 KiB
[binary U ] chromeos-base/tast-cmd-0.0.1-r205::chromiumos [0.0.1-r204::chromiumos] USE="cros_host" 3696 KiB
[binary U ] chromeos-base/shill-client-0.0.1-r1558::chromiumos [0.0.1-r1557::chromiumos] USE="cros_host -asan -coverage -cros-debug -fuzzer -msan {-test} -ubsan" 42 KiB
[binary U ] net-print/cups-2.2.8-r19::chromiumos [2.1.4-r18::chromiumos] USE="acl cros_host python seccomp ssl threads -X -dbus -debug -java -kerberos -lprng-compat -pam -selinux -static-libs -systemd -upst
art -usb -xinetd -zeroconf" ABI_X86="(64) -32 (-x32)" LINGUAS="-ca -cs -de -es -fr -it -ja -ru" PYTHON_TARGETS="python2_7" 960 KiB
[binary U ] chromeos-base/ec-utils-0.0.1-r5167::chromiumos [0.0.1-r5165::chromiumos] USE="cros_host -cr50_onboard -cr50_utils -static -unibuild -updater_utils" EC_FIRMWARE="-atlas -atlas_ish -bds -chell -ch
ell_pd -cheza -coral -cr50 -cyan -dingdong -dragonegg -elm -eve -eve_fp -extra_atlas -extra_atlas_ish -extra_bds -extra_chell -extra_chell_pd -extra_cheza -extra_coral -extra_cr50 -extra_cyan -extra_dingdong -ex
tra_dragonegg -extra_elm -extra_eve -extra_eve_fp -extra_fizz -extra_glados -extra_glados_pd -extra_glkrvp -extra_gru -extra_grunt -extra_hadoken -extra_hammer -extra_hoho -extra_host -extra_jerry -extra_kalista
-extra_kevin -extra_kukui -extra_llama -extra_lux -extra_meowth -extra_meowth_fp -extra_minimuffin -extra_nami -extra_nami_fp -extra_nautilus -extra_nefario -extra_nocturne -extra_nocturne_fp -extra_oak -extra_
oak_pd -extra_octopus -extra_plankton -extra_poppy -extra_rammus -extra_reef -extra_rowan -extra_ryu -extra_ryu_p4p5 -extra_ryu_sh -extra_ryu_sh_loader -extra_samus -extra_samus_pd -extra_scarlet -extra_soraka -
extra_staff -extra_strago -extra_twinkie -extra_wand -extra_whiskers -extra_zinger -extra_zoombini -fizz -glados -glados_pd -glkrvp -gru -grunt -hadoken -hammer -hoho -host -jerry -kalista -kevin -kukui -llama -
lux -meowth -meowth_fp -minimuffin -nami -nami_fp -nautilus -nefario -nocturne -nocturne_fp -oak -oak_pd -octopus -plankton -poppy -rammus -reef -rowan -ryu -ryu_p4p5 -ryu_sh -ryu_sh_loader -samus -samus_pd -sca
rlet -soraka -staff -strago -twinkie -wand -whiskers -zinger -zoombini" 73 KiB
[binary U ] chromeos-base/ec-devutils-0.0.2-r3241::chromiumos [0.0.2-r3239::chromiumos] USE="cros_host" PYTHON_TARGETS="python2_7" 212 KiB
[binary U ] sys-apps/pv-1.6.6::portage-stable [1.3.4::portage-stable] USE="nls -debug%" LINGUAS="(-de%) (-fr%) (-pl%) (-pt%)" 68 KiB
[binary U ] dev-util/crosutils-0.0.1-r2186::chromiumos [0.0.1-r2185::chromiumos] USE="cros_host" 86 KiB
And then running update_chroot was able to update the toolchains. Everything seems to be ok now. Was the crosutils or toolchain-utils upgraded needed to go with glibc?
,
Nov 12
toolchain-utils should not have anything to with glibc. So maybe it is related with crosutils package but my guess would be something python/portage related.
,
Nov 26
can this be closed?
,
Nov 27
Ben, marking as won't fix. Please re-open if necessary. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by manojgupta@chromium.org
, Nov 12