All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kever Yang <kever.yang@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] build fail due to dependence error
Date: Thu, 28 Jun 2018 16:38:19 +0800	[thread overview]
Message-ID: <19ab9dda-5133-829a-4c4f-6988926a4a9f@rock-chips.com> (raw)
In-Reply-To: <83756b95-d066-2667-f036-24fd1097541e@rock-chips.com>

Hi Simon,

        Do you have any idea about this error?


CC      lib/asm-offsets.s
  CC      arch/arm/lib/asm-offsets.s
fixdep: error opening config file: arch/arm/include/asm/arch/hardware.h: No such file or directory
Kbuild:64: recipe for target 'arch/arm/lib/asm-offsets.s' failed
make[1]: *** [arch/arm/lib/asm-offsets.s] Error 2
make[1]: *** 正在等待未完成的任务....
  CHK     include/config.h
Makefile:1340: recipe for target 'prepare0' failed

Thanks,
- Kever

On 06/01/2018 05:59 PM, Kever Yang wrote:
> Hi Guys,
>
>      I met below error from time to time when build U-Boot project.
>
> fixdep: error opening config file: arch/arm/include/asm/arch/hardware.h: No such file or directory
>
>     The folder 'arch/arm/include/asm/arch' is a link for
> 'arch/arm/include/asm/arch-rockchip',
>
> which is dynamic generate by build system, I thinks there should be some
> dependency issue?
>
>     How to fix this kind of issue?
>
>
> Thanks,
>
> - Kever
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot

  reply	other threads:[~2018-06-28  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01  9:59 [U-Boot] build fail due to dependence error Kever Yang
2018-06-28  8:38 ` Kever Yang [this message]
2018-06-28  8:41   ` Dr. Philipp Tomsich
2018-06-30  4:19     ` Simon Glass
2018-07-02  7:54       ` Kever Yang
2018-07-02  8:23         ` Dr. Philipp Tomsich
2018-07-09  2:39           ` Simon Glass
2018-07-09  5:26             ` Masahiro Yamada
2018-07-09  7:18               ` Patrick DELAUNAY
2018-07-09  8:36                 ` Dr. Philipp Tomsich

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=19ab9dda-5133-829a-4c4f-6988926a4a9f@rock-chips.com \
    --to=kever.yang@rock-chips.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.