All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-fdt
Date: Tue, 9 May 2017 19:59:13 -0400	[thread overview]
Message-ID: <20170509235913.GX12511@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ3yEZQDehxZ+iEV+kaUHGwSiGzkxXuC94StHL8T46cRqA@mail.gmail.com>

On Tue, May 09, 2017 at 04:53:36PM -0600, Simon Glass wrote:

> Hi Tom,
> 
> Here's the conversion to use the upstream pylibfdt implementation.
> 
> 
> The following changes since commit 85ea850976daea57c8045f3569566fad5ce9fe0f:
> 
>   p1_p2_rdb: Fix unused variable warning (2017-05-09 09:11:04 -0400)
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-fdt.git
> 
> for you to fetch changes up to 8fbd55f0f8730e3a6994798f4e533138d15be6aa:
> 
>   fdt: Drop fdt_select.py (2017-05-09 14:56:19 -0600)
> 

NAK.  I get:
$ ./test/py/test.py --bd sandbox --build
make O=/home/trini/work/u-boot/u-boot/build-sandbox -s sandbox_defconfig
make O=/home/trini/work/u-boot/u-boot/build-sandbox -s -j8
Assembler messages:
Fatal error: can't create
build/temp.linux-x86_64-2.7/../lib/libfdt/fdt.o: No such file or
directory
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
make[2]: *** [tools/_libfdt.so] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [tools] Error 2
make: *** [sub-make] Error 2
Exit code: 2

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170509/efd733e0/attachment.sig>

  reply	other threads:[~2017-05-09 23:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 22:53 [U-Boot] Please pull u-boot-fdt Simon Glass
2017-05-09 23:59 ` Tom Rini [this message]
2017-05-10 14:29   ` Simon Glass
2017-05-19  0:40   ` Simon Glass
  -- strict thread matches above, loose matches on Subject: below --
2019-11-05 12:23 Simon Glass
2019-11-05 23:12 ` Tom Rini
2017-09-15 19:31 Simon Glass
2017-09-17  1:42 ` Tom Rini
2017-04-10 20:52 Simon Glass
2017-04-11 13:18 ` Tom Rini
2017-01-14 17:14 Simon Glass
2017-01-14 20:57 ` Tom Rini
2016-11-25 16:51 Simon Glass
2016-11-25 19:39 ` Simon Glass
2016-11-26 14:25 ` Tom Rini
2016-10-24  3:01 Simon Glass
2016-10-24 15:24 ` Tom Rini
2016-10-11 20:29 Simon Glass
2016-10-12 14:13 ` Tom Rini
2016-10-12 14:43   ` Simon Glass
2016-10-13  9:43     ` Keerthy
2016-10-13 11:47       ` Keerthy
2016-10-13 12:11         ` Tom Rini
2016-10-13 12:36           ` Simon Glass
2016-10-13 12:38         ` Simon Glass
2016-10-13 12:39           ` Keerthy
2016-10-13 12:43             ` Simon Glass
2016-10-13 14:24   ` Simon Glass
2016-10-13 14:33     ` Tom Rini
2016-10-13 14:38       ` Simon Glass
2016-10-13 14:59     ` Keerthy
2016-10-13 15:08       ` Simon Glass
2016-10-13 15:34         ` Keerthy
2016-01-22 21:42 Simon Glass
2016-01-23  0:55 ` Tom Rini
2015-10-03 14:45 Simon Glass
2015-10-03 14:50 ` Tom Rini
2015-10-02 14:14 Simon Glass
2015-07-20 14:04 Simon Glass
2015-07-21 13:50 ` Tom Rini
2015-06-05 16:08 Simon Glass
2015-06-06 13:27 ` Tom Rini
2015-04-24 15:37 Simon Glass
2015-04-28 14:51 ` Tom Rini
2015-04-10 14:16 Simon Glass
2015-04-10 18:49 ` Tom Rini
2015-02-18 13:09 Simon Glass
2015-02-19  4:09 ` Tom Rini

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=20170509235913.GX12511@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.