• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1459 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM335X: Build error using snapshot options under revision 07.03.00.005 (5.4 kernel based)

miken valabdas
Prodigy 20 points

Part Number: PROCESSOR-SDK-AM335X

Hi,

I have followed the document 'software-dl.ti.com/.../Overview_Building_the_SDK.html' in order to setup a build environment for revision 07.03.00.005' (5.4 kernel based) using the source package snapshot option.

I am getting the following error message while trying to compile using the command: MACHINE=am335x-evm bitbake tisdk-base-image

---------------------------------------------------------------------------------------------------------------
miken@miken-Precision-5560:~/Travaux/Ethernet-PRU/TI/sdk-Build/tisdk/build$ MACHINE=am335x-evm bitbake tisdk-base-image
Loading cache: 100% |##############################################################################################| Time: 0:00:00
Loaded 4109 entries from dependency cache.
WARNING: No recipes available for:
/home/miken/Travaux/Ethernet-PRU/TI/sdk-Build/tisdk/sources/meta-arago/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-20.04"
TARGET_SYS = "arm-linux-gnueabi"
MACHINE = "am335x-evm"
DISTRO = "arago"
DISTRO_VERSION = "2020.09"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-processor-sdk = "HEAD:c467012684e57c914c4070238987e931f329da15"
meta-arago-distro
meta-arago-extras = "HEAD:ee6ff44d90945429051c8d9573c8b60705104149"
meta-qt5 = "HEAD:b4d24d70aca75791902df5cd59a4f4a54aa4a125"
meta-virtualization = "HEAD:89abc62b47f6f20db9d00a8ec9b2c1b6b60ac3f9"
meta-networking
meta-python
meta-oe
meta-gnome
meta-filesystems = "HEAD:389757a7494221fea1d8437e9a01c6e4fb4700af"
meta-ti = "HEAD:02a53f48b9bdb242185204610610f2209bc92ca6"
meta-arm
meta-arm-toolchain = "HEAD:c4f04f3fb66f8f4365b08b553af8206372e90a63"
meta = "HEAD:707036d4ec12ef1a260adcef78627b26e32e6540"

Initialising tasks: 100% |#########################################################################################| Time: 0:00:01
Sstate summary: Wanted 579 Found 0 Missed 579 Current 616 (0% match, 51% complete)
NOTE: Executing Tasks
WARNING: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Failed to fetch URL git://gitlab.gnome.org/GNOME/mobile-broadband-provider-info.git;protocol=https, attempting MIRRORS if available
ERROR: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Fetcher failure: Unable to find revision 90f3fe28aa25135b7e4a54a7816388913bfd4a2a in branch master even from upstream
ERROR: mobile-broadband-provider-info-1_20201225-r0 do_fetch: Fetcher failure for URL: 'git://gitlab.gnome.org/GNOME/mobile-broadband-provider-info.git;protocol=https'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/miken/Travaux/Ethernet-PRU/TI/sdk-Build/tisdk/build/arago-tmp-external-arm-glibc/work/armv7at2hf-neon-linux-gnueabi/mobile-broadband-provider-info/1_20201225-r0/temp/log.do_fetch.2896087
ERROR: Task (/home/miken/Travaux/Ethernet-PRU/TI/sdk-Build/tisdk/sources/oe-core/meta/recipes-connectivity/mobile-broadband-provider-info/mobile-broadband-provider-info_git.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1779 tasks of which 1658 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/miken/Travaux/Ethernet-PRU/TI/sdk-Build/tisdk/sources/oe-core/meta/recipes-connectivity/mobile-broadband-provider-info/mobile-broadband-provider-info_git.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
---------------------------------------------------------------------------------------------------------------

Using the snapshot option, all required packages should be downloaded locally from TI server into '/tisdk/downloads/'.

The folder '/tisdk/downloads/' seems to have all repo that are used to build Arago.
In fact, there is a git repo '/tisdk/downloads/git2/gitlab.gnome.org.GNOME.mobile-broadband-provider-info.git'. The git tag ‘20201225’ along with the requested commit '90f3fe28aa25135b7e4a54a7816388913bfd4a2a' that is required from 'mobile-broadband-provider-info_git.bb' are present.
I don't understand the compilation failure as the setup seems to be good.

I have tried on 2 different machines (Ubuntu 18.04 and Ubuntu 20.04). Both gave me the same result.
Any thought from your side would be greatly appreciated.

Regards,

  • 0
    TI__Guru**** 181906 points

    Hi,

    I am routing your query to our Yocto expert for comments.

  • 0
    TI__Guru 70822 points
    miken valabdas said:
    The git tag ‘20201225’ along with the requested commit '90f3fe28aa25135b7e4a54a7816388913bfd4a2a' that is required from 'mobile-broadband-provider-info_git.bb' are present.

    Those warning messages can be confusing, especially when you only really see the "Unable to fetch URL from any source" piece. It sounds much more dramatic then what's actually happening. If you look at the Git-fetcher utility part of Yocto you see that it will try to checkout a specific branch as well, not just the commit itself (which would suffice I argue). What has been happening is that upstream branch names are changing in many instances ('master' -> 'main'), breaking many existing SDK builds, especially older ones. It is a bit of a pain to deal with but usually one can figure out what needs to be fixed:

    • It may help looking at the latest upstream version of a certain recipe, chances are the change was already made there (because somebody ran into it already). And then take the change from there and backport it. Note, I'd only take the URL/Git related changes, not an entire newer recipe, as otherwise you introduce additional variables and potential incompatibilities.

    • Googling to find the official Git repository may help too, and after some browser-based exploration it often becomes evident quickly what needs to change, such as a branch name, an URL, or perhaps the transport protocol Git uses (often support for the 'git' transport gets dropped in favor of 'https')

    At some point I expect us to re-start hosting/mirroring more of those Yocto source (and build artifacts) to reduce the amount of breakage over time, that's something in the works.

    Regards, Andreas