From: "Quentin Schulz" <quentin.schulz@streamunlimited.com>
To: paruchuribhavyasree@gmail.com
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] ERRORS while building customized yocto image for Raspberrypi #yocto
Date: Mon, 27 Jul 2020 10:23:49 +0200 [thread overview]
Message-ID: <20200727082349.vji4hpki47etvwuw@qschulz> (raw)
In-Reply-To: <11928.1595650329560242513@lists.yoctoproject.org>
Hi Bhavya,
On Fri, Jul 24, 2020 at 09:12:09PM -0700, paruchuribhavyasree@gmail.com wrote:
> Hi Quentin
>
> I tried changing it but facing same kind of error during Build.
>
Your S = "${WORKDIR}" is probably wrong then.
Is there only a directory "at the root" of the tarball? I mean if you
untar it, do you get one directory where all your source code is? In
that case, if the subdirectory is named "gsm-${PV}" (replace PV with the
correct and full number), you don't need to define S because the default
should be just enough IIRC.
Otherwise, S = "${WORKDIR}/<whatever_name_of_the_dir_in_gsm-${PV}.tar.gz_is>"
Finally, since your license is not in the tarball (but it should really
be actually), you need to prefix your LIC_FILES_CHKSUM with "../"
otherwise the license won't be found.
Moreover, you can't reassign twice the same variable and expect them to
be merged. That's what you did for SRC_URI but I missed that you also
did it for LICENSE, if it's dual licensed: LICENSE = "GNUC | GPLv3" or
LICENSE = "GNUC & GPLv3", the meaning is obviously not the same but you
only can know what to put there.
N.B.: You still need the SRC_URI as I gave you in an earlier mail.
Quentin
prev parent reply other threads:[~2020-07-27 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 12:59 ERRORS while building customized yocto image for Raspberrypi #yocto paruchuribhavyasree
2020-07-24 13:14 ` [yocto] " Quentin Schulz
2020-07-25 4:12 ` paruchuribhavyasree
2020-07-27 8:23 ` Quentin Schulz [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=20200727082349.vji4hpki47etvwuw@qschulz \
--to=quentin.schulz@streamunlimited.com \
--cc=paruchuribhavyasree@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox