Re: gcc update breaking existing chroots ?

[Anush Elangovan(அனுஷ்)]

from the right address now:

On Thu, May 3, 2012 at 3:02 PM, Anush Elangovan(அனுஷ்) <an...@google.com> wrote:
> Seen this on couple of workstations after syncing to ToT
>
> INFO    : Updating chroot
> Determining required toolchain updates...
> Updating packages:
> ['<=cross-armv7a-cros-linux-gnueabi/gcc-4.6.3-r19',
> '<=cross-x86_64-cros-linux-gnu/gcc-4.6.3-r19',
> '<=cross-i686-pc-linux-gnu/gcc-4.6.3-r19',
> '<=cross-arm-none-eabi/gcc-4.6.3-r19', '<=sys-devel/gcc-4.6.3-r19']
>
> INFO: RunCommand: ['/home/blah/trunk/chromite/bin/parallel_emerge',
> '--oneshot', '--update', '--getbinpkg', '--usepkgonly',
> '<=cross-armv7a-cros-linux-gnueabi/gcc-4.6.3-r19',
> '<=cross-x86_64-cros-linux-gnu/gcc-4.6.3-r19',
> '<=cross-i686-pc-linux-gnu/gcc-4.6.3-r19',
> '<=cross-arm-none-eabi/gcc-4.6.3-r19', '<=sys-devel/gcc-4.6.3-r19']
> Starting fast-emerge.
>  Building package <=cross-armv7a-cros-linux-gnueabi/gcc-4.6.3-r19
> <=cross-x86_64-cros-linux-gnu/gcc-4.6.3-r19
> <=cross-i686-pc-linux-gnu/gcc-4.6.3-r19
> <=cross-arm-none-eabi/gcc-4.6.3-r19 <=sys-devel/gcc-4.6.3-r19 on root
> Calculating deps...
> Deps calculated in 0m0.9s
> [binary     U  ] cross-arm-none-eabi/gcc-4.6.2-r18 [4.6.2-r17]
> Pending 0/1, Fetching 1/1, [Time 0m4.0s Load 0.32 0.14 0.58]
> Fetched cross-arm-none-eabi/gcc-4.6.2-r18 in 2.51s
> Started cross-arm-none-eabi/gcc-4.6.2-r18 (logged in /tmp/gcc-4.6.2-r18-eIqtnb)
> Pending 0/1, Building 1/1, [Time 1m6.6s Load 0.96 0.36 0.62]
> Completed cross-arm-none-eabi/gcc-4.6.2-r18 (in 1m53.1s)
> Pending 0/1, [Time 1m59.7s Load 1.03 0.47 0.65]
> Merge complete
> Done
>  * gcc-config: Could not locate 'i686-pc-linux-gnu-4.6.3' in '/etc/env.d/gcc/' !
> cros_setup_toolchains: Unhandled exception:
> Traceback (most recent call last):
>  File "/home/blah/trunk/chromite/bin/cros_setup_toolchains", line 67,
> in <module>
>    ret = target()
>  File "/home/blah/trunk/chromite/scripts/cros_setup_toolchains.py",
> line 613, in main
>    UpdateToolchains(options.usepkg, options.deleteold,
> options.hostonly, targets)
>  File "/home/blah/trunk/chromite/scripts/cros_setup_toolchains.py",
> line 578, in UpdateToolchains
>    SelectActiveToolchains(targets, CONFIG_TARGET_SUFFIXES)
>  File "/home/blah/trunk/chromite/scripts/cros_setup_toolchains.py",
> line 541, in SelectActiveToolchains
>    cros_build_lib.RunCommand(cmd, print_cmd=False)
>  File "/home/blah/trunk/chromite/lib/cros_build_lib.py", line 431, in
> RunCommand
>    raise RunCommandError(msg, cmd_result)
> chromite.lib.cros_build_lib.RunCommandError: Failed command
> "['gcc-config', 'i686-pc-linux-gnu-4.6.3']", cwd=None, extra env=None

[Mike Frysinger]

someone else mentioned this in irc. i imagine related to Zdenek's
recent conversion to use the python code for toolchain management.

prob should start a bug :)
-mike

[Zdenek Behan]

Whee!

That must've been me. :(

Reverting now, asking questions later.

[asharif]

zbehan, when did you submit your CL? I also submitted a CL to update gcc.git's master branch today to fix a bug. I ran it through remote trybots to make sure it worked, though: https://gerrit.chromium.org/gerrit/#change,21695

[Zdenek Behan]

On Fri, May 4, 2012 at 12:09 AM, asharif <ash...@chromium.org> wrote:

zbehan, when did you submit your CL? I also submitted a CL to update gcc.git's master branch today to fix a bug. I ran it through remote trybots to make sure it worked, though: https://gerrit.chromium.org/gerrit/#change,21695

Moments ago. It seems there's a problem with gcc-config or its use. I don't have an idea what's wrong yet, but I already reverted mine, so if anyone sees a problem, please sync and retry.

[Anush Elangovan(அனுஷ்)]

On Thu, May 3, 2012 at 3:20 PM, Anush Elangovan(அனுஷ்) <an...@google.com> wrote:

> On Thu, May 3, 2012 at 3:19 PM, Zdenek Behan <zbe...@chromium.org> wrote:
>> On Fri, May 4, 2012 at 12:09 AM, asharif <ash...@chromium.org> wrote:
>>>
>>> zbehan, when did you submit your CL? I also submitted a CL to update
>>> gcc.git's master branch today to fix a bug. I ran it through remote trybots
>>> to make sure it worked,
>>> though: https://gerrit.chromium.org/gerrit/#change,21695
>>
>>
>> Moments ago. It seems there's a problem with gcc-config or its use. I don't
>> have an idea what's wrong yet, but I already reverted mine, so if anyone
>> sees a problem, please sync and retry.
>

works now