From: "Trevor Woerner" <twoerner@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [meta-freescale] [PATCH] u-boot: set B directory for imx5's
Date: Tue, 11 Feb 2020 13:06:08 -0500 [thread overview]
Message-ID: <20200211180608.GA29200@linux-uys3> (raw)
In-Reply-To: <CAP9ODKrNM+n=MVaHjFf7qxkw1zYpKr7wAN77V1o9ZiaehHXbZw@mail.gmail.com>
On Tue 2020-02-11 @ 02:17:03 PM, Otavio Salvador wrote:
> On Tue, Feb 11, 2020 at 12:12 PM Trevor Woerner <twoerner@gmail.com> wrote:
> > On Tue 2020-02-11 @ 10:47:46 AM, Otavio Salvador wrote:
> > > On Mon, Feb 10, 2020 at 8:14 PM Trevor Woerner <twoerner@gmail.com> wrote:
> > > > The imx5* machines need separate S and B directories to build u-boot-fslc
> > > > otherwise the build fails with:
> > > >
> > > > | make[1]: *** No rule to make target '/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git/arch//cpu/u-boot.lds', needed by 'u-boot.lds'. Stop.
> > > >
> > > > Build-tested with imx51evk, imx53ard, and imx53qsb.
> > > >
> > > > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
>
> Please open an issue on github?
Okay.
> IIRC, we are using different build directories for S and B so I am
> wondering why it is failing.
This is what I'm getting:
$ bitbake virtual/bootloader -e | grep "^B="
B="/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git"
$ bitbake virtual/bootloader -e | grep "^S="
S="/z/build-master/meta-freescale/build/tmp-glibc/work/imx53qsb-oe-linux-gnueabi/u-boot-fslc/v2019.07+gitAUTOINC+ca0ab15271-r0/git"
prev parent reply other threads:[~2020-02-11 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 23:13 [PATCH] u-boot: set B directory for imx5's Trevor Woerner
2020-02-11 13:47 ` [meta-freescale] " Otavio Salvador
2020-02-11 15:12 ` Trevor Woerner
2020-02-11 17:17 ` Otavio Salvador
2020-02-11 18:06 ` Trevor Woerner [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=20200211180608.GA29200@linux-uys3 \
--to=twoerner@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).