Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Radek Dostál" <radek.dostal@streamunlimited.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot.inc: properly specify CC for EXTRA_OEMAKE
Date: Thu, 5 Nov 2015 16:19:49 +0100	[thread overview]
Message-ID: <563B7395.1010104@streamunlimited.com> (raw)
In-Reply-To: <CAP9ODKqFTU76yL_DqeNku4G3502R00C4K8qwdEtCp5zk1pmJRw@mail.gmail.com>

Hi Otavio,

> Nack!
>
> The U-Boot is close to the Linux kernel regarding the use of the
> compiler and does a huge set of handling internally to properly pass
> options depending on the SoC, arch and others.
>
> This build error has been fixed in new U-Boot releases and if the
> board required an old version (and cannot be updated) the fix should
> be done on the recipe and not on the common file as it can change,
> behind the scenes, what is in use for several recipes without notice.

Thanks a lot for your valuable input. I was not aware of the fact that 
it was fixed in the upstream already. If you know the commit out of your 
head, it would be great if you could share it.

Thanks,
Radek


  parent reply	other threads:[~2015-11-05 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 16:06 [PATCH] u-boot.inc: properly specify CC for EXTRA_OEMAKE Radek Dostal
2015-11-05 13:14 ` Otavio Salvador
2015-11-05 13:16   ` Carlos Rafael Giani
2015-11-05 14:22     ` Otavio Salvador
2015-11-05 14:23       ` Carlos Rafael Giani
2015-11-10 13:09         ` Tom Rini
2015-11-11  3:59           ` Khem Raj
2015-11-11 12:37             ` Tom Rini
2015-11-11 16:21               ` Khem Raj
2015-11-05 15:19   ` Radek Dostál [this message]
2015-11-05 15:32     ` Burton, Ross
2015-11-05 15:47     ` Otavio Salvador
2015-11-05 16:02       ` Radek Dostál

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=563B7395.1010104@streamunlimited.com \
    --to=radek.dostal@streamunlimited.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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