devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Markus Mayer <mmayer@broadcom.com>
Cc: DTC Mailing List <devicetree-compiler@vger.kernel.org>,
	 David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 1/1] Makefile: only use compiler flags when supported
Date: Wed, 9 Oct 2024 15:15:32 -0600	[thread overview]
Message-ID: <CAFLszTifpySKvBD6rSx9S++2d7qPiZeBWWyqEw3jq-Aeg=xkXQ@mail.gmail.com> (raw)
In-Reply-To: <CAGt4E5upXi4URn+JZworFJFPch=7iBot4E1b6WBCUZ3p8JBx7A@mail.gmail.com>

Hi Markus,

On Wed, 9 Oct 2024 at 14:43, Markus Mayer <mmayer@broadcom.com> wrote:
>
> Hi Simon,
>
> On Tue, 8 Oct 2024 at 18:57, Simon Glass <sjg@chromium.org> wrote:
> >
> > > diff --git a/Makefile b/Makefile
> > > index f1f0ab368cd3..febdca5742c5 100644
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -3,6 +3,26 @@
> > >  # Device Tree Compiler
> > >  #
> > >
> > > +# try-run and cc-option were stolen from the Linux kernel
> > > +TMPOUT = .tmp_$$$$
> > > +# try-run
> > > +# Usage: option = $(call try-run, $(CC)...-o "$$TMP",option-ok,otherwise)
> > > +# Exit code chooses option. "$$TMP" serves as a temporary file and is
> > > +# automatically cleaned up.
> > > +try-run = $(shell set -e;              \
> > > +       TMP=$(TMPOUT)/tmp;              \
> > > +       mkdir -p $(TMPOUT);             \
> > > +       trap "rm -rf $(TMPOUT)" EXIT;   \
> > > +       if ($(1)) >/dev/null 2>&1;      \
> > > +       then echo "$(2)";               \
> > > +       else echo "$(3)";               \
> > > +       fi)
> > > +
> > > +# cc-option
> > > +# Usage: cflags-y += $(call cc-option,-march=winchip-c6,-march=i586)
> > > +cc-option = $(call try-run, \
> > > +       $(CC) -Werror $(1) -c -x c /dev/null -o "$$TMP",$(1),$(2))
> > > +
> > >  #
> > >  # Version information will be constructed in this order:
> > >  # DTC_VERSION release version as MAJOR.MINOR.PATCH
> > > @@ -18,9 +38,12 @@ CONFIG_LOCALVERSION =
> > >  ASSUME_MASK ?= 0
> > >
> > >  CPPFLAGS = -I libfdt -I . -DFDT_ASSUME_MASK=$(ASSUME_MASK)
> > > +# Warnings where we need to check they are supported
> > > +OPT_WARNINGS = $(call cc-option,-Wsuggest-attribute=format)
> >
> > This is fine, but you should be able to use the existing cc-option in U-Boot
>
> I seem to be missing something... how does U-Boot factor in here?
>
> My use case is to build a standalone version of dtc with clang for
> x86. This dtc is meant to run on the build host. U-Boot sources are
> not involved.

Sorry, I saw this in the middle of a bunch of U-Boot reviews and
didn't notice :-)

Regards,
Simon

  reply	other threads:[~2024-10-09 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 21:41 [PATCH 0/1] DTC v1.7.1 Build Error Markus Mayer
2024-10-08 21:41 ` [PATCH 1/1] Makefile: only use compiler flags when supported Markus Mayer
2024-10-09  1:57   ` Simon Glass
2024-10-09 20:43     ` Markus Mayer
2024-10-09 21:15       ` Simon Glass [this message]
2024-10-09 21:18         ` Markus Mayer
2024-10-16  9:32   ` David Gibson

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='CAFLszTifpySKvBD6rSx9S++2d7qPiZeBWWyqEw3jq-Aeg=xkXQ@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=mmayer@broadcom.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).