u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: satish kumar <gsatish.ldd@gmail.com>
To: u-boot@lists.denx.de
Cc: Jagan Teki <jagan@amarulasolutions.com>,
	Vignesh R <vigneshr@ti.com>, Marek <marex@denx.de>,
	 Simon <simon.k.r.goldschmidt@gmail.com>,
	Tien Fong <tien.fong.chee@intel.com>,
	 Kok Kiang <kok.kiang.hea@intel.com>,
	Raaj <raaj.lokanathan@intel.com>,
	 Dinesh <dinesh.maniyam@intel.com>,
	Boon Khai <boon.khai.ng@intel.com>,
	 Alif <alif.zakuan.yuslaimi@intel.com>,
	Teik Heng <teik.heng.chong@intel.com>,
	 Hazim <muhammad.hazim.izzat.zamri@intel.com>,
	 Jit Loon Lim <jit.loon.lim@intel.com>,
	Sieu Mun Tang <sieu.mun.tang@intel.com>
Subject: u-boot compilation failure for Sifive unmatched board
Date: Fri, 30 Jun 2023 22:52:47 +0530	[thread overview]
Message-ID: <CAK1XJzWofn5+OE7qCyf3nTb+hevULoAVss5dG2OzwbMh0C=YVA@mail.gmail.com> (raw)

Hi all
This is Satish, compiling u-boot code based on the reference page:
https://github.com/carlosedp/riscv-bringup/blob/master/unmatched/Readme.md#install-toolchain-to-build-kernel

u-boot is failing with following commit id & its tag is
commit d637294e264adfeb29f390dfc393106fd4d41b17 (HEAD, tag: v2022.01)

Last tag working is:
commit b46dd116ce03e235f2a7d4843c6278e1da44b5e1 (HEAD, tag: v2021.04)

Error log is:
scripts/dtc/pylibfdt/libfdt_wrap.c:149:11: fatal error: Python.h: No
such file or directory
 # include <Python.h>
           ^~~~~~~~~~
compilation terminated.

Does that I am using invalid tag or invalid link
please support me to fix the issue.

Thanks & Regards
Satish G

             reply	other threads:[~2023-06-30 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 17:22 satish kumar [this message]
2023-06-30 18:49 ` u-boot compilation failure for Sifive unmatched board Fabio Estevam

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='CAK1XJzWofn5+OE7qCyf3nTb+hevULoAVss5dG2OzwbMh0C=YVA@mail.gmail.com' \
    --to=gsatish.ldd@gmail.com \
    --cc=alif.zakuan.yuslaimi@intel.com \
    --cc=boon.khai.ng@intel.com \
    --cc=dinesh.maniyam@intel.com \
    --cc=jagan@amarulasolutions.com \
    --cc=jit.loon.lim@intel.com \
    --cc=kok.kiang.hea@intel.com \
    --cc=marex@denx.de \
    --cc=muhammad.hazim.izzat.zamri@intel.com \
    --cc=raaj.lokanathan@intel.com \
    --cc=sieu.mun.tang@intel.com \
    --cc=simon.k.r.goldschmidt@gmail.com \
    --cc=teik.heng.chong@intel.com \
    --cc=tien.fong.chee@intel.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.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 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 NNTP newsgroup(s).