From: Oleksij Rempel <linux@rempel-privat.de>
To: Peter Mamonov <pmamonov@gmail.com>,
barebox@lists.infradead.org, pvizeli@syshack.ch
Subject: Re: scripts/dtc/fdtget: No such file or directory
Date: Thu, 9 Aug 2018 07:33:10 +0200 [thread overview]
Message-ID: <c582856b-519d-f9c5-fe53-7573443eef3a@rempel-privat.de> (raw)
In-Reply-To: <20180808162250.avlghvty7eh4ndhi@localhost.localdomain>
[-- Attachment #1.1.1: Type: text/plain, Size: 1109 bytes --]
Hi,
Am 08.08.2018 um 18:22 schrieb Peter Mamonov:
> Hi,
>
> After "8a8982541 scripts/dtc: Update to upstream version 1.4.6"
> scripts/dtc/Makefile lacks rule for scripts/dtc/fdtget, which causes
> scripts/gen-dtb-s to complain:
>
> $ make
> ...
> scripts/gen-dtb-s: line 24: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 27: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 34: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 37: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 24: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 27: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 34: scripts/dtc/fdtget: No such file or directory
> scripts/gen-dtb-s: line 37: scripts/dtc/fdtget: No such file or directory
>
> Yet a build finishes ok.
I noticed same issue yesterday,
this happens only if you build barebox not in the source directory.
Probably make files should copy this scripts as well.
--
Regards,
Oleksij
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-09 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 16:22 Peter Mamonov
2018-08-09 5:33 ` Oleksij Rempel [this message]
2018-08-09 6:58 ` Sascha Hauer
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=c582856b-519d-f9c5-fe53-7573443eef3a@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=barebox@lists.infradead.org \
--cc=pmamonov@gmail.com \
--cc=pvizeli@syshack.ch \
/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