Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] llvm3.2: new recipe
Date: Sun, 02 Jun 2013 11:55:16 +0200	[thread overview]
Message-ID: <51AB1684.1080500@juszkiewicz.com.pl> (raw)
In-Reply-To: <1370165592-15697-1-git-send-email-net147@gmail.com>

W dniu 02.06.2013 11:33, Jonathan Liu pisze:
> +def get_llvm_arch(d):
> +    import bb;
> +
> +    arch = bb.data.getVar('TARGET_ARCH', d, 1)
> +
> +    if arch == "x86_64" or arch == "i486" or arch == "i586" or arch == "i686":
> +        arch = "x86"
> +    elif arch == "x86_64":
> +        arch = "x86_64"
> +    elif arch == "arm":
> +        arch = "arm"
> +    elif arch == "mipsel" or arch == "mips":
> +        arch = "mips"
> +    elif arch == "powerpc" or arch == "powerpc64":
> +        arch = "powerpc"
> +    else:
> +        bb.warn("%s does not support %s yet" % (bb.data.getVar('PN', d, 1), arch) );
> +
> +    return arch

Can we get rid of such blocks? They are worthless and only generate
extra support questions when OE newbies use OE with 'not supported'
architectures.


  reply	other threads:[~2013-06-02  9:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02  9:33 [meta-oe][PATCH] llvm3.2: new recipe Jonathan Liu
2013-06-02  9:55 ` Marcin Juszkiewicz [this message]
2013-06-03  4:30   ` Jonathan Liu
2013-06-11  7:48   ` Khem Raj
2013-06-11  7:55     ` Marcin Juszkiewicz
2013-06-11  8:03       ` Khem Raj
2013-06-11  8:54         ` Marcin Juszkiewicz
2013-06-11  9:07           ` Khem Raj
2013-06-11  9:10             ` Marcin Juszkiewicz

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=51AB1684.1080500@juszkiewicz.com.pl \
    --to=marcin@juszkiewicz.com.pl \
    --cc=openembedded-devel@lists.openembedded.org \
    /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