From: Grant Edwards <grant.b.edwards@gmail.com>
To: u-boot@lists.denx.de
Subject: Re: Compile only changed files when doing 'make'?
Date: Wed, 26 Jan 2022 15:09:15 -0000 (UTC) [thread overview]
Message-ID: <ssro6r$2gf$1@ciao.gmane.io> (raw)
In-Reply-To: ssp68j$bos$1@ciao.gmane.io
On 2022-01-25, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I'm working on a Renesas supplied port of U-Boot, and it seems that
> 'make' always compiles every single (configured) source file instead
> compiling only the source files that have been changed since the
> previous 'make'.
This problem appears to be caused by an incompatibility between the
Kbuild infrastructure2 and GNU make-4.3. Switching to make-4.2.1
solved the problem.
The U-Boot source tree we're using is the v2017.01 branch. It's the
latest supported by the Renesas board support files. I'm not very
happy they haven't contributed the supported upstream to make it
easier to support newer versions. I've asked Renesas about this, and
they have no plans to either support a newer version of U-Boot or
contribute their support files. :/
I assume that this Kbuild incompatibility with make-4.3 has been fixed
in newer versions of U-Boot.
If this Kbuild problem is familiar to anybody, and you know where the
fix was made, I'd appreciate a pointer so that I can back-port that
fix to my v2017.01 sources.
Thanks...
--
Grant
prev parent reply other threads:[~2022-01-26 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:50 Compile only changed files when doing 'make'? Grant Edwards
2022-01-25 17:34 ` Tom Rini
2022-01-26 15:09 ` Grant Edwards [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='ssro6r$2gf$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox