All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
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 15:23:48 +0100	[thread overview]
Message-ID: <563B6674.1030106@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKrhSmSsx1aSY0oyoqYeV8zHm_NVtp3mH=4X8zX-BEmL3w@mail.gmail.com>

On 11/05/2015 03:22 PM, Otavio Salvador wrote:
> Hello Carlos,
>
> On Thu, Nov 5, 2015 at 11:16 AM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> So, this is because of the TOOLCHAIN_OPTIONS ?
>> Also, what about the ${CC} ? Right now it won't work properly with clang for
>> example.
> The clang is problem might involve us to rework something but all this
> needs to be based on last U-Boot releases; we shouldn't put
> workarounds and hacks on OE-Core without good reasons.
>
> Has the clang been tested with 2015.10?
>

Still, then I'd add something to output an error message like "U-Boot 
can only be compiled with gcc". Right now, the error messages that would 
occur would be highly confusing and misleading.


  reply	other threads:[~2015-11-05 14:23 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 [this message]
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
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=563B6674.1030106@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --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 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.