All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kelly <mkelly@xevo.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-clang] llvm-config cross-compile improvements
Date: Mon, 20 Mar 2017 11:41:20 -0700	[thread overview]
Message-ID: <0b02cc8c-2a2c-51aa-4394-b44847c37d13@xevo.com> (raw)
In-Reply-To: <CAMKF1srJC1vitok6sf1WLggHgSRga6eHYGm7JM324nP7b51ZSA@mail.gmail.com>

On 03/20/2017 10:37 AM, Khem Raj wrote:
> On Sat, Mar 18, 2017 at 8:29 PM, Martin Kelly <mkelly@xevo.com> wrote:
>> Hi,
>>
>> This patch series fixes a number of issues I hit when trying to use the
>> meta-clang llvm-config to cross-compile a project that uses CMake, calling
>> into llvm-config, to determine compile flags. With the series applied, the
>> cross compile successfully builds and runs. Please let me know if you have
>> any concerns or if there is something I missed, and I will fix it up.
>>
>> The following changes since commit c9c74d269ba79abbc20919de96f1eb2b8a81edec:
>>
>>   clang/compiler-rt: Fix nativesdk builds break compiler-rt dep for clang
>> (2017-03-16 22:54:02 -0700)
>>
>> are available in the git repository at:
>>
>>   https://github.com/surround-io/meta-clang
>>
>> for you to fetch changes up to 7d294bc2548ade23b7d25761d73769e712617c51:
>>
>
>
> can you send a simple gh pull request please ?
>

Done; sorry, from the meta-clang readme, I thought it was asking for 
pull requests to go over openembedded-devel, but I'm happy with Github too.


      reply	other threads:[~2017-03-20 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19  3:29 [meta-clang] llvm-config cross-compile improvements Martin Kelly
2017-03-20 17:37 ` Khem Raj
2017-03-20 18:41   ` Martin Kelly [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=0b02cc8c-2a2c-51aa-4394-b44847c37d13@xevo.com \
    --to=mkelly@xevo.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.