From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/3] kbuild: always use relative path for __FILE__
Date: Fri, 13 Oct 2017 09:53:03 -0400 [thread overview]
Message-ID: <20171013135303.GI12015@bill-the-cat> (raw)
In-Reply-To: <CAK7LNARjx7Cr8U0rV41BNPNmLL2-upPuJEHWaeRzdp+6d9ZMdA@mail.gmail.com>
On Fri, Oct 13, 2017 at 09:21:19PM +0900, Masahiro Yamada wrote:
> 2017-10-13 21:11 GMT+09:00 Tom Rini <trini@konsulko.com>:
> > On Fri, Oct 13, 2017 at 06:51:42PM +0900, Masahiro Yamada wrote:
> >
> >> We discussed the __FILE__ problem when U-Boot is built out of tree.
> >> https://www.mail-archive.com/u-boot at lists.denx.de/msg242852.html
> >>
> >> The deeper your build directory is located, the larger
> >> your U-Boot image becomes.
> >> If your platform has memory footprint limit, this is a problem.
> >>
> >> Recently, I submitted the following patches to Kbuild ML.
> >> (no RFC, this time)
> >> https://patchwork.kernel.org/patch/10001419/
> >> https://patchwork.kernel.org/patch/10001409/
> >>
> >> I consider them for Linux 4.15 unless there is
> >> a strong objection or a problem report.
> >>
> >> This series is a port for U-Boot.
> >>
> >> If Tom wants to pick this up earlier, it is OK.
> >> If not in hurry, you can wait for the activity in Linux.
> >> Either will do.
> >
> > Yay. I plan to pick these up after v2017.11 has been released, so no
> > need to re-spin this if it stops applying cleanly until we're closer to
> > release. Thanks!
> >
>
> Good.
>
> According to this:
> http://phb-crystal-ball.org/
>
> The MW for v4.15 will open 2017-11-12.
>
> So, the next MW for U-Boot and Linux will be almost lined up.
>
> You will be able to apply it more confidently
> if Linus pulls the Linux counterpart.
>
> Until then, I will test it in linux-next.
FWIW, a world build is:
https://gist.github.com/trini/ad0f55b9f46997fd11801aac48bf0c10
I wonder why we see size increase in a few cases? In both cases, the
obj directory is /tmp/something/01_of_.. (or 04_of_..)/current/..
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171013/82f1380c/attachment.sig>
next prev parent reply other threads:[~2017-10-13 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 9:51 [U-Boot] [PATCH v2 0/3] kbuild: always use relative path for __FILE__ Masahiro Yamada
2017-10-13 9:51 ` [U-Boot] [PATCH v2 1/3] kbuild: Get rid of KBUILD_STR Masahiro Yamada
2017-10-13 9:51 ` [U-Boot] [PATCH v2 2/3] kbuild: add stringify helper to quote a string passed to C files Masahiro Yamada
2017-10-13 9:51 ` [U-Boot] [PATCH v2 3/3] kbuild: redefine __FILE__ as relative path from $(srctree) if possible Masahiro Yamada
2017-10-13 12:11 ` [U-Boot] [PATCH v2 0/3] kbuild: always use relative path for __FILE__ Tom Rini
2017-10-13 12:21 ` Masahiro Yamada
2017-10-13 13:53 ` Tom Rini [this message]
2017-10-13 17:37 ` Masahiro Yamada
2017-10-13 18:35 ` Masahiro Yamada
2017-10-13 21:39 ` Tom Rini
2017-10-15 9:48 ` Masahiro Yamada
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=20171013135303.GI12015@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox