All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: make O=directory parameter
Date: Thu, 25 Feb 2021 10:35:21 -0500	[thread overview]
Message-ID: <20210225153521.GQ10169@bill-the-cat> (raw)
In-Reply-To: <fb68cb30-3053-d86c-7bad-95d2103f23ff@gmail.com>

On Thu, Feb 25, 2021 at 12:50:47PM +1100, Fred 1 wrote:

> like in the linux kernel build
> 
> make O=builds/arm
> 
> builds the result to the specified output directory
> 
> 
> is this supposed to work for uboot also ?
> 
> doesn't seem to work for me, i've fetched older tar files and same problem
> 
> maybe my environment?
> 
> ??? fedora32
> 
> ??? 5.10.13-100.fc32.x86_64
> 
> ??? GNU Make 4.2.1
> 
> the O=<dir>? does mostly work on older uboot like from ~2010 though....
> 
> 
> thought i'd ask as debugging the make process is,well umm...horrible,
> 
> (i've inserted some extra debug print codes in gnu make (it self no code to
> be praised about!
> 
> esp when so much open source depends on it!!)
> 
> so atm, a bit of a rabbit hole........should I persist?

Can you provide a sample failure?  The last "make O=... fails" I saw was
because they were passing ARCH= which isn't valid for U-Boot and
specifically breaks if you're say building for an aarch64 platform as in
the linux kernel you would do ARCH=arm64 but it's all "arm" here.
Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210225/53974b2b/attachment.sig>

  reply	other threads:[~2021-02-25 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  1:50 make O=directory parameter Fred 1
2021-02-25 15:35 ` Tom Rini [this message]
2021-02-26 11:27   ` Fred 1
2021-02-26 12:58     ` Tom Rini
2021-03-04  0:27       ` Fred 1

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=20210225153521.GQ10169@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.