cros_sdk --nouse-image --url=https://gs.cdn.openfyde.cn/chromiumos-sdk/cros-sdk-2022.04.11.135343.tar.xz
之后出现
(inside) export BOARD=amd64-openfyde # 对于 rpi4-openfyde 需要 export BOARD=rpi4-openfyde
(inside) setup_board --board=${BOARD}
这些在什么时候输入？
出现这个画面意味着 cros_sdk 正在初始化，有不少事情要做，截图表明这个初始化的工作还没有完成。初始化完成之后，你将被带入 cros_sdk 创建的 chroot 环境，也就是 (inside) 所表达的意思。
带有 (inside) 的命令需要在 chroot 内执行。
(cr) (release-R102-14695.B/(5fc6a3c…))
这个就是相当于 （inside）？
对的
* This package will overwrite one or more files that may belong to other
* packages (see list below). Add either "collision-protect" or "protect-
* owned" to FEATURES in make.conf if you would like the merge to abort
* in cases like this. See the make.conf man page for more information
* about these features. You can use a command such as `portageq owners /
* <filename>` to identify the installed package that owns a file. If
* portageq reports that only one package owns a file then do NOT file a
* bug report. A bug report is only useful if it identifies at least two
* or more packages that are known to install the same file(s). If a
* collision occurs and you can not explain where the file came from then
* you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /build/amd64-openfyde/usr/bin/awk
* /build/amd64-openfyde/bin/sh
* Package 'chromeos-base/chromeos-base-1-r12' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* Messages for package app-benchmarks/sysbench-1.0.10 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/app-benchmarks:sysbench-1.0.10:20231226-072504.log
* Fallback PaX marking -m
* /build/amd64-openfyde/tmp/portage/app-benchmarks/sysbench-1.0.10/work/sysbench-1.0.10/src/sysbench
* Messages for package dev-python/lxml-4.2.5 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/dev-python:lxml-4.2.5:20231226-075649.log
* dev-python/beautifulsoup for Support for BeautifulSoup as a parser backend
* dev-python/cssselect for Translates CSS selectors to XPath 1.0 expressions
* Messages for package net-wireless/hostapd-2.10_pre-r188 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/net-wireless:hostapd-2.10_pre-r188:20231226-080438.log
* Your configuration for net-wireless/hostapd-2.10_pre-r188 has been saved in
* /etc/portage/savedconfig/net-wireless/hostapd-2.10_pre-r188 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* Messages for package sys-libs/pam-1.3.1-r2 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-libs:pam-1.3.1-r2:20231226-081915.log
* Some software with pre-loaded PAM libraries might experience
* warnings or failures related to missing symbols and/or versions
* after any update. While unfortunate this is a limit of the
* implementation of PAM and the software, and it requires you to
* restart the software manually after the update.
*
* You can get a list of such software running a command like
* lsof / | egrep -i 'del.*libpam\.so'
*
* Alternatively, simply reboot your system.
* Messages for package net-dialup/ppp-2.4.9-r6 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/net-dialup:ppp-2.4.9-r6:20231226-082000.log
* Unable to find kernel sources at /build/amd64-generic/usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Pon, poff and plog scripts have been supplied for experienced users.
* Users needing particular scripts (ssh,rsh,etc.) should check out the
* /usr/share/doc/ppp-2.4.9-r6/scripts directory.
* Messages for package app-admin/sudo-1.9.8_p2 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/app-admin:sudo-1.9.8_p2:20231226-082042.log
* Warning: tmpfiles.d not processed on ROOT != /. If you do not use
* a service manager supporting tmpfiles.d, you need to run
* the following command after booting (or chroot-ing with all
* appropriate filesystems mounted) into the ROOT:
*
* tmpfiles --create
*
* Failure to do so may result in missing runtime directories
* and failures to run programs or start services.
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
* Messages for package sys-apps/util-linux-2.36.2-r3 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-apps:util-linux-2.36.2-r3:20231226-082000.log
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
* The agetty util now clears the terminal by default. You
* might want to add --noclear to your /etc/inittab lines.
* Messages for package dev-libs/glib-2.68.3-r2 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/dev-libs:glib-2.68.3-r2:20231226-082805.log
* Updating of GIO modules cache skipped due to cross-compilation.
* You might want to run gio-querymodules manually on the target for
* your final image for performance reasons and re-run it when packages
* installing GIO modules get upgraded or added to the image.
* Messages for package sys-fs/xfsprogs-4.14.0-r3 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-fs:xfsprogs-4.14.0-r3:20231226-083643.log
* gen_usr_ldscript: Please migrate to usr-ldscript.eclass
* Messages for package sys-kernel/chromeos-kernel-5_4-5.4.207-r3110 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-kernel:chromeos-kernel-5_4-5.4.207-r3110:20231226-063856.log
* Using kernel config: /mnt/host/source/src/overlays/overlay-amd64-openfyde/kconfig/fydeos_def_r102_5.4_test
* - enabling Enable ACPI AC config
* - disabling framebuffer console config
* - enabling Enable IIO service config
* - enabling Support running virtual machines with KVM config
* - enabling CDC MBIM driver config
* - enabling Transparent Hugepage Support config
* - enabling 802.1Q VLAN config
* - disabling VT console config
* Messages for package sys-auth/nss-mdns-0.13-r1 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-auth:nss-mdns-0.13-r1:20231226-091825.log
* You have to modify your name service switch look up file to enable
* multicast DNS lookups. If you wish to resolve only IPv6 addresses
* use mdns6. For IPv4 addresses only, use mdns4. To resolve both
* use mdns. Keep in mind that mdns will be slower if there are no
* IPv6 addresses published via mDNS on the network. There are also
* minimal (mdns?_minimal) libraries which only lookup .local hosts
* and 169.254.x.x addresses.
*
* Add the appropriate mdns into the hosts line in /etc/nsswitch.conf.
* An example line looks like:
* hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
*
* If you want to perform mDNS lookups for domains other than the ones
* ending in .local, add them to /etc/mdns.allow.
* Messages for package media-libs/fontconfig-2.13.0-r11 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/media-libs:fontconfig-2.13.0-r11:20231226-092814.log
* Please make fontconfig configuration changes using `eselect
* fontconfig`. Any changes made to /etc/fonts/fonts.conf will be
* overwritten. If you need to reset your configuration to upstream
* defaults, delete the directory
* /build/amd64-openfyde/etc/fonts/conf.d/ and re-emerge fontconfig.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/fontconfig-2.13.0-r11/README.gentoo*
* for future reference)
* Messages for package dev-vcs/git-2.31.0-r1 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/dev-vcs:git-2.31.0-r1:20231226-093209.log
* Please read /usr/share/bash-completion/completions/git for Git bash command
* completion.
* Please read /usr/share/git/git-prompt.sh for Git bash prompt
* Note that the prompt bash code is now in that separate script
* These additional scripts need some dependencies:
* git-quiltimport : dev-util/quilt
* git-instaweb : || ( www-servers/lighttpd www-servers/apache www-servers/nginx )
* Messages for package net-misc/dhcpcd-7.2.5-r5 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/net-misc:dhcpcd-7.2.5-r5:20231226-094130.log
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
* Messages for package sys-fs/lvm2-2.02.187-r4 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/sys-fs:lvm2-2.02.187-r4:20231226-094257.log
* Notice that "use_lvmetad" setting is enabled with USE="udev" in
* /etc/lvm/lvm.conf, which will require restart of udev, lvm, and lvmetad
* if it was previously disabled.
* Make sure the "lvm" init script is in the runlevels:
* # rc-update add lvm boot
*
* Make sure to enable lvmetad in /etc/lvm/lvm.conf if you want
* to enable lvm autoactivation and metadata caching.
* Messages for package dev-libs/libusb-1.0.22-r3 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/dev-libs:libusb-1.0.22-r3:20231226-095031.log
* gen_usr_ldscript: Please migrate to usr-ldscript.eclass
* Messages for package net-misc/usbip-4.19-r8 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/net-misc:usbip-4.19-r8:20231226-095646.log
* For using USB/IP you need to enable USBIP_VHCI_HCD in the client
* machine's kernel config and USBIP_HOST on the server.
* Messages for package chromeos-base/chromeos-fonts-0.0.1-r49 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r49:20231226-100037.log
* This package will overwrite one or more files that may belong to other
* packages (see list below). Add either "collision-protect" or "protect-
* owned" to FEATURES in make.conf if you would like the merge to abort
* in cases like this. See the make.conf man page for more information
* about these features. You can use a command such as `portageq owners /
* <filename>` to identify the installed package that owns a file. If
* portageq reports that only one package owns a file then do NOT file a
* bug report. A bug report is only useful if it identifies at least two
* or more packages that are known to install the same file(s). If a
* collision occurs and you can not explain where the file came from then
* you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /build/amd64-openfyde/usr/share/fonts/roboto/.uuid
* /build/amd64-openfyde/usr/share/fonts/tibt-jomolhari/.uuid
* /build/amd64-openfyde/usr/share/fonts/crosextra/.uuid
* /build/amd64-openfyde/usr/share/fonts/lohit-cros/.uuid
* /build/amd64-openfyde/usr/share/fonts/croscore/.uuid
* /build/amd64-openfyde/usr/share/fonts/ko-nanum/.uuid
* /build/amd64-openfyde/usr/share/fonts/notocjk/.uuid
* /build/amd64-openfyde/usr/share/fonts/noto/.uuid
* Package 'chromeos-base/chromeos-fonts-0.0.1-r49' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* Messages for package media-gfx/imagemagick-7.0.8.42 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/media-gfx:imagemagick-7.0.8.42:20231226-095155.log
* For security reasons, a policy.xml file was installed in /etc/ImageMagick-7
* which will prevent the usage of the following coders by default:
*
* - PS
* - PS2
* - PS3
* - EPS
* - PDF
* - XPS
* Messages for package media-gfx/sane-backends-1.1.1-r1 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/media-gfx:sane-backends-1.1.1-r1:20231226-102921.log
* If you are using a USB scanner, add all users who want
* to access your scanner to the "scanner" group.
* Messages for package dev-go/perfetto-protos-17.0-r632 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/dev-go:perfetto-protos-17.0-r632:20231226-105646.log
* Could not find "/mnt/host/source/src/third_party/../aosp/external/perfetto".
* The CROS_WORKON_LOCALNAME for this ebuild should be updated
* to be relative to "/mnt/host/source/src/third_party".
* Messages for package chromeos-base/chrome-icu-102.0.5005.179_rc-r1 merged to /build/amd64-openfyde/:
* Log file: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:chrome-icu-102.0.5005.179_rc-r1:20231226-105746.log
* ERROR: chromeos-base/chrome-icu-102.0.5005.179_rc-r1::chromiumos failed (configure phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 4632: Called die
* The specific snippet of code:
* "${gn[@]}" || die
*
* Build log: /build/amd64-openfyde/tmp/portage/logs/chromeos-base:chrome-icu-102.0.5005.179_rc-r1:20231226-105746.log
* Stable log symlink: /build/amd64-openfyde/tmp/portage/chromeos-base/chrome-icu-102.0.5005.179_rc-r1/temp/build.log
* CWD: /build/amd64-openfyde/tmp/portage/chromeos-base/chrome-icu-102.0.5005.179_rc-r1/work/chrome-icu-102.0.5005.179_rc
* S: /build/amd64-openfyde/tmp/portage/chromeos-base/chrome-icu-102.0.5005.179_rc-r1/work/chrome-icu-102.0.5005.179_rc
18:58:29 ERROR : 2023年 12月 26日 星期二 18:58:29 CST
18:58:29 ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND
18:58:29 ERROR : 464225 4 464225 05:42:00 00:00:00 0.0 -bash
18:58:29 ERROR : 509505 464225 509505 05:16:13 00:00:01 0.0 \_ python3 /mnt/host/source/chromite/bin/build_packages --board=amd64-openfyde --nowithautotest --autosetgov --nouse_any_chrome
18:58:29 ERROR : 509505 509505 519326 05:12:42 00:00:00 0.0 \_ bash /mnt/host/source/src/scripts/build_packages.sh --script-is-run-only-by-chromite-and-not-users --board amd64-openfyde --board_root /build/amd64-openfyde --jobs 4 --nouse_any_chrome --nowithautotest
18:58:29 ERROR : 509505 519326 2707300 00:00 00:00:00 0.0 \_ bash /mnt/host/source/src/scripts/build_packages.sh --script-is-run-only-by-chromite-and-not-users --board amd64-openfyde --board_root /build/amd64-openfyde --jobs 4 --nouse_any_chrome --nowithautotest
18:58:29 ERROR : 509505 2707300 2707301 00:00 00:00:00 0.0 \_ ps f -o pgid,ppid,pid,etime,cputime,%cpu,command
18:58:29 ERROR : Arguments of 519326: '--script-is-run-only-by-chromite-and-not-users' '--board' 'amd64-openfyde' '--board_root' '/build/amd64-openfyde' '--jobs' '4' '--nouse_any_chrome' '--nowithautotest'
18:58:29 ERROR : Backtrace: (most recent call is last)
18:58:29 ERROR : build_packages.sh:395:main(), called: die_err_trap
18:58:29 ERROR :
18:58:29 ERROR : Command failed:
18:58:29 ERROR : Command '( if [[ "${FLAGS_run_remoteexec}" -eq "${FLAGS_TRUE}" ]]; then
18:58:29 ERROR : info "Starting RBE reproxy."; bootstrap="${RECLIENT_DIR}/bootstrap --cfg=${REPROXY_CFG} --re_proxy=${RECLIENT_DIR}/reproxy"; ${bootstrap}; trap "${bootstrap} --shutdown" EXIT;
18:58:29 ERROR : else
18:58:29 ERROR : if [[ "${FLAGS_run_goma}" -eq "${FLAGS_TRUE}" ]]; then
18:58:29 ERROR : info "Starting goma compiler_proxy."; goma_ctl="${GOMA_DIR:-${HOME}/goma}/goma_ctl.py"; "${goma_ctl}" restart; trap "'${goma_ctl}' stop" EXIT;
18:58:29 ERROR : fi;
18:58:29 ERROR : fi; info_run sudo -E "${EMERGE_CMD[@]}" "${EMERGE_FLAGS[@]}" "${PACKAGES[@]}" --useoldpkg-atoms="${CRITICAL_SDK_PACKAGES[*]}" --rebuild-exclude="${CRITICAL_SDK_PACKAGES[*]}" )' exited with nonzero code: 1
build_packages: Unhandled exception:
Traceback (most recent call last):
File "/mnt/host/source/chromite/service/sysroot.py", line 667, in BuildPackages
cros_build_lib.run(cmd, extra_env=extra_env)
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 938, in run
raise RunCommandError(msg, cmd_result)
chromite.lib.cros_build_lib.RunCommandError: return code: 1; command: bash PosixPath('/mnt/host/source/src/scripts/build_packages.sh') --script-is-run-only-by-chromite-and-not-users --board amd64-openfyde --board_root /build/amd64-openfyde --jobs 4 --nouse_any_chrome --nowithautotest
cmd=['bash', PosixPath('/mnt/host/source/src/scripts/build_packages.sh'), '--script-is-run-only-by-chromite-and-not-users', '--board', 'amd64-openfyde', '--board_root', '/build/amd64-openfyde', '--jobs', '4', '--nouse_any_chrome', '--nowithautotest'], extra env={'CROS_METRICS_DIR': '/tmp/tmpm36uc2qg'}
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/host/source/chromite/scripts/build_packages.py", line 412, in main
sysroot.BuildPackages(build_target, board_root, opts.build_run_config)
File "/mnt/host/source/chromite/service/sysroot.py", line 671, in BuildPackages
str(e), e.result, exception=e, packages=failed_pkgs)
chromite.lib.sysroot_lib.PackageInstallError: return code: 1; command: bash PosixPath('/mnt/host/source/src/scripts/build_packages.sh') --script-is-run-only-by-chromite-and-not-users --board amd64-openfyde --board_root /build/amd64-openfyde --jobs 4 --nouse_any_chrome --nowithautotest
return code: 1; command: bash PosixPath('/mnt/host/source/src/scripts/build_packages.sh') --script-is-run-only-by-chromite-and-not-users --board amd64-openfyde --board_root /build/amd64-openfyde --jobs 4 --nouse_any_chrome --nowithautotest
cmd=['bash', PosixPath('/mnt/host/source/src/scripts/build_packages.sh'), '--script-is-run-only-by-chromite-and-not-users', '--board', 'amd64-openfyde', '--board_root', '/build/amd64-openfyde', '--jobs', '4', '--nouse_any_chrome', '--nowithautotest'], extra env={'CROS_METRICS_DIR': '/tmp/tmpm36uc2qg'}
Failed Packages: chromeos-base/chrome-icu-102.0.5005.179_rc-r1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib64/python3.6/urllib/request.py", line 1349, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/usr/lib64/python3.6/http/client.py", line 1287, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib64/python3.6/http/client.py", line 1333, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib64/python3.6/http/client.py", line 1282, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib64/python3.6/http/client.py", line 1042, in _send_output
self.send(msg)
File "/usr/lib64/python3.6/http/client.py", line 980, in send
self.connect()
File "/usr/lib64/python3.6/http/client.py", line 1440, in connect
super().connect()
File "/usr/lib64/python3.6/http/client.py", line 952, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/lib64/python3.6/socket.py", line 724, in create_connection
raise err
File "/usr/lib64/python3.6/socket.py", line 713, in create_connection
sock.connect(sa)
OSError: [Errno 101] Network is unreachable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/host/source/chromite/bin/build_packages", line 208, in <module>
DoMain()
File "/mnt/host/source/chromite/bin/build_packages", line 204, in DoMain
commandline.ScriptWrapperMain(FindTarget)
File "/mnt/host/source/chromite/lib/commandline.py", line 1037, in ScriptWrapperMain
ret = target(argv[1:])
File "/mnt/host/source/chromite/scripts/build_packages.py", line 416, in main
'https://chromiumos-status.appspot.com/current?format=raw')
File "/usr/lib64/python3.6/urllib/request.py", line 223, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib64/python3.6/urllib/request.py", line 526, in open
response = self._open(req, data)
File "/usr/lib64/python3.6/urllib/request.py", line 544, in _open
'_open', req)
File "/usr/lib64/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
File "/usr/lib64/python3.6/urllib/request.py", line 1392, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/usr/lib64/python3.6/urllib/request.py", line 1351, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 101] Network is unreachable>
出现了好多错误
test最后出现这个。
partx: specified range <1:0> does not make sense
An error occurred in your build so your latest output directory is invalid.
Would you like to delete the output directory (y/N)? y
你试图编译的是 r102 这个分支吗？这个有点老了，建议编译 r114 目前最新的。还是说这是无意为之
版本没啥要求，就看先过一遍流程。
是不是跟这个错误有关？
gclient sync --nohooks -vvv和gclient --runhooks -vvv
Updating depot_tools…
depot_tools update failed. Couldn’t fetch main branch.
Retry later or reclone depot_tools
fatal: 无法访问 'https://chromium.googlesource.com/chromium/tools/depot_tools.git/'：Failed to connect to chromium.googlesource.com port 443 after 131069 ms: 连接超时
首先确认 shell 中设置了环境变量 export DEPOT_TOOLS_UPDATE=0。
另外确认已经下载了 r102_distfiles_cache.tar.gz 并解压至 cros chroot 用到的 cache 目录。
export DEPOT_TOOLS_UPDATE=0
这个应该没有 每次 都做到。
./cache文件夹里面有distfiles sdks两个文件夹
distfiles文件夹里面也有很多文件，应该就是已经完成了这一步
这个 / path / to / 要根据自己修改吗？
这个文件明明在的啊。
是的，需要根据你的 depot_tools 的实际目录，设置 PATH 环境变量。