S32G-how to solve building yocto error

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32G-how to solve building yocto error

3,325件の閲覧回数
seeu
Contributor III

Dear all,

    I am following the S32G2_LInuxBSP_33.0 User Manual to use command ''bitbake fsl-image-auto'',face below error,how to resolve this error?

 

 

vmuser@ubuntu:~/fsl-auto-yocto-bsp/build_s32g274ardb2$ bitbake fsl-image-auto
Loading cache: 100% |###########################################| Time: 0:00:00
Loaded 886 entries from dependency cache.
WARNING: /home/vmuser/fsl-auto-yocto-bsp/sources/meta-alb/recipes-kernel/pfe/pfe_1.0.0.bb: Unable to get checksum for pfe SRC_URI entry s32g_pfe_class.fw: file could not be found
WARNING: /home/vmuser/fsl-auto-yocto-bsp/sources/meta-alb/recipes-kernel/pfe/pfe_1.0.0.bb: Unable to get checksum for pfe SRC_URI entry s32g_pfe_util.fw: file could not be found
WARNING: /home/vmuser/fsl-auto-yocto-bsp/sources/poky/meta/recipes-core/coreutils/coreutils_8.32.bb: Variable key RDEPENDS_${PN} ( attr) replaces original key RDEPENDS_coreutils ( ${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}).
Parsing recipes: 100% |#########################################| Time: 0:05:26
Parsing of 3301 .bb files complete (592 cached, 2709 parsed). 4901 targets, 289 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.48.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-18.04"
TARGET_SYS = "aarch64-fsl-linux"
MACHINE = "s32g274ardb2"
DISTRO = "fsl-auto"
DISTRO_VERSION = "33.0"
TUNE_FEATURES = "aarch64 armv8a crc cortexa53 crypto"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "HEAD:6a751048e50c00261d99c2d8d69534f7a8da38a9"
meta-oe
meta-multimedia
meta-python = "HEAD:f3f7a5f1a4713f145107bb043e0d14cb3a51c62f"
meta-python2 = "HEAD:3fae17aece0e6d82f56965fe501bf7080c671df8"
meta-networking
meta-gnome
meta-filesystems
meta-webserver
meta-perl
meta-xfce = "HEAD:f3f7a5f1a4713f145107bb043e0d14cb3a51c62f"
meta-virtualization = "HEAD:fa093228c02c4a42da1f9abb77c4c57d70d5a212"
meta-optee = "HEAD:fb96032b38e3064290ab0891238c92d47a45f151"
meta-security = "HEAD:3daf99fd138b0eebe864bbe1b9c71241d97c4512"
meta-freescale = "HEAD:41d4f625c6db7a778f0f9a735c2cb48e023bc49b"
meta-alb = "HEAD:0b34c281628625665829d1969d86bc179a8c6d96"

NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.0/x86_64-nativesdk-libc.tar.xz;sha256sum=5ec5... (will check PREMIRRORS first)
Initialising tasks: 100% |######################################| Time: 0:00:03
Checking sstate mirror object availability: 100% |##############| Time: 0:00:03
Sstate summary: Wanted 2180 Found 0 Missed 2180 Current 0 (0% match, 0% complete)
NOTE: Executing Tasks
WARNING: rsync-native-3.2.3-r0 do_fetch: Failed to fetch URL https://download.samba.org/pub/rsync/src/rsync-3.2.3.tar.gz, attempting MIRRORS if available
WARNING: linux-libc-headers-5.8-r0 do_fetch: Failed to fetch URL https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.8.tar.xz, attempting MIRRORS if available
WARNING: binutils-cross-aarch64-2.35.1-r0 do_fetch: Failed to fetch URL git://sourceware.org/git/binutils-gdb.git;branch=binutils-2_35-branch;protocol=git, attempting MIRRORS if available
ERROR: binutils-cross-aarch64-2.35.1-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="1805"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/vmuser/fsl-auto-yocto-bsp/sources/poky/scripts:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/usr/bin/aarch64-fsl-linux:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/usr/bin/aarch64-fsl-linux/crossscripts:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/usr/sbin:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/usr/bin:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/sbin:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/recipe-sysroot-native/bin:/home/vmuser/fsl-auto-yocto-bsp/sources/poky/bitbake/bin:/home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/hosttools"; export HOME="/home/vmuser"; git -c core.fsyncobjectfiles=0 remote failed with exit code 128, output:
fatal: not a git repository (or any of the parent directories): .git

ERROR: binutils-cross-aarch64-2.35.1-r0 do_fetch: Fetcher failure for URL: 'git://sourceware.org/git/binutils-gdb.git;branch=binutils-2_35-branch;protocol=git'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/vmuser/fsl-auto-yocto-bsp/build_s32g274ardb2/tmp/work/x86_64-linux/binutils-cross-aarch64/2.35.1-r0/temp/log.do_fetch.66774
ERROR: Task (/home/vmuser/fsl-auto-yocto-bsp/sources/poky/meta/recipes-devtools/binutils/binutils-cross_2.35.1.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 244 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/vmuser/fsl-auto-yocto-bsp/sources/poky/meta/recipes-devtools/binutils/binutils-cross_2.35.1.bb:do_fetch
Summary: There were 6 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

0 件の賞賛
返信
2 返答(返信)

3,178件の閲覧回数
Shyamsunder
Contributor I

Hello,

is your yocto build error is resolved?  Can you please let us know the solution if it resolved already.

Thanks:)

Shyamsunder K

 

0 件の賞賛
返信

3,307件の閲覧回数
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

 

This fetch error means that the server that have the package is unavailable or you have a problem with your proxy, try in a moment again.

 

Regards

0 件の賞賛
返信