From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Pankaj Vinadrao Joshi <pankaj.vj@exaleapsemi.com>
Subject: Re: [OE-core] Error while building image for 5.4.y on RPI4
Date: Fri, 12 Jun 2020 17:34:45 -0700 [thread overview]
Message-ID: <3022466.YH7JXIEmOa@tyche> (raw)
In-Reply-To: <Y4nb.1591945376060563369.5YNj@lists.openembedded.org>
On Friday, June 12, 2020 12:02:56 AM PDT Pankaj Vinadrao Joshi wrote:
> Hi,
> i am trying to build an image for RPI4 for 5.4.y kernel but i am getting
> following error , i
>
> Initialising tasks: 100%
> |##########################################################################
> ############################################################################
> #############| Time: 0:00:04 Sstate summary: Wanted 1094 Found 0 Missed 1094
> Current 1154 (0% match, 51% complete) NOTE: Executing Tasks
> WARNING: libfm-extra-1.3.1-r0 do_fetch: Failed to fetch URL
> https://downloads.sourceforge.net/pcmanfm/libfm-1.3.1.tar.xz, attempting
> MIRRORS if available *WARNING:
> linux-raspberrypi-1_5.4.40+gitAUTOINC+97badb4bae-r0 do_fetch: Failed to
> fetch URL git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y,
> attempting MIRRORS if available* *ERROR:
> linux-raspberrypi-1_5.4.40+gitAUTOINC+97badb4bae-r0 do_fetch: Fetcher
> failure: Unable to find revision 97badb4baeb8999263a9bc2fa85c3060ffff344b
> in branch rpi-5.4.y even from upstream* *ERROR:
> linux-raspberrypi-1_5.4.40+gitAUTOINC+97badb4bae-r0 do_fetch: Fetcher
> failure for URL: 'git://github.com/raspberrypi/linux.git;branch=rpi-5.4.y'.
> Unable to fetch URL from any source.* *ERROR: Logfile of failure stored in:
> /home/pankaj/Oe-Raspberrypi4/tmp-glibc/work/raspberrypi4-oe-linux-gnueabi/l
> inux-raspberrypi/1_5.4.40+gitAUTOINC+97badb4bae-r0/temp/log.do_fetch.10175*
> ERROR: Task
> (/home/pankaj/meta-raspberry/meta-raspberrypi/recipes-kernel/linux/linux-ra
> spberrypi_5.4.bb:do_fetch) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 2294 tasks of which 1551 didn't need to be rerun and 1 failed.
>
> This my linux-raspberrypi_5.4.bb file
>
> LINUX_VERSION ?= "5.4.40"
> LINUX_RPI_BRANCH ?= "rpi-5.4.y"
>
> SRCREV = "97badb4baeb8999263a9bc2fa85c3060ffff344b"
>
> require linux-raspberrypi_5.4.inc
>
> SRC_URI +=
> "file://0001-perf-Make-perf-able-to-build-with-latest-libbfd.patch \
> file://0001-Revert-selftests-bpf-Skip-perf-hw-events-test-if-the.patch \
> file://0002-Revert-selftests-bpf-Fix-perf_buffer-test-on-systems.patch \
> file://0001-selftest-bpf-Use-CHECK-macro-instead-of-RET_IF.patch \
> file://powersave.cfg \
> "
>
> pankaj@exaleap-Inspiron-3584:~/Oe-Raspberrypi4$ bitbake -e | grep
> ^PREFERRED_VERSION_linux-raspberrypi
> PREFERRED_VERSION_linux-raspberrypi="5.4.%"
>
> am i missing anything,why i am getting this error can someone help??
upstream has not yet make 5.4 as defualt kernel for rpi until they do so they
keep rebasing it unfortunately which means meta-raspberrypi has to keep
updating SRCREVs,
you can cherrypick https://github.com/agherzan/meta-raspberrypi/pull/654
until its merged
prev parent reply other threads:[~2020-06-13 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 7:02 Error while building image for 5.4.y on RPI4 Pankaj Vinadrao Joshi
2020-06-12 7:11 ` [OE-core] " Denys Dmytriyenko
2020-06-13 0:34 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3022466.YH7JXIEmOa@tyche \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pankaj.vj@exaleapsemi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.