Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 3/3] llvm2.9: try to fix thumb build and disable it after failure
Date: Sat, 20 Apr 2013 12:24:17 +0200	[thread overview]
Message-ID: <20130420102417.GL2489@jama> (raw)
In-Reply-To: <20130420094605.GA13784@mi.fu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

On Sat, Apr 20, 2013 at 11:46:05AM +0200, Henning Heinold wrote:
> Hi Martin,
> 
> sorry to say but arm support on 2.9 is broken in serval way. I put

Yes I also got this feeling :/.

> it in mostly for testing purpose. Maybe with upcoming llvm 3.3 the arm situation
> will be better.

Well when I was checking if there is thumb fix later in git repo for
backport I haven't found it, so we'll probably need to fix thumb also
for 3.3..

I wanted to add 2.9 only to be able to remove both from meta-java
without loosing anything and this at least fixes build so I don't have
another recipe in error in jenkins builds.

Also mesa documentation says that 2.9 is recommended llvm version (but
it supports different versions too)

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-04-20 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 14:02 [meta-oe][PATCH 1/3] llvm2.9: Import from meta-java Martin Jansa
2013-04-19 14:02 ` [meta-oe][PATCH 2/3] llvm2.9: fix build with gcc-4.7 Martin Jansa
2013-04-19 14:02 ` [meta-oe][PATCH 3/3] llvm2.9: try to fix thumb build and disable it after failure Martin Jansa
2013-04-20  9:46   ` Henning Heinold
2013-04-20 10:24     ` Martin Jansa [this message]

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=20130420102417.GL2489@jama \
    --to=martin.jansa@gmail.com \
    --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