Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-commits@lists.openembedded.org"
	<openembedded-commits@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Khem Raj : lttng-modules_2.3.3.bb: Fix build on ARM/gcc-4.9
Date: Mon, 5 May 2014 03:04:11 +0200	[thread overview]
Message-ID: <20140505010411.GJ2486@jama> (raw)
In-Reply-To: <CAMKF1sqAEB77eo6dQzkZgqqk1CQkWoa_YFP4y_ZNwteJoRz7KA@mail.gmail.com>

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

On Sun, May 04, 2014 at 04:53:14PM -0700, Khem Raj wrote:
> On Sun, May 4, 2014 at 7:50 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> Update the structure to work with immutable bio_vecs
> >
> > Is this really 4.9 specific? It's failing with the same error message in
> > every qemuarm world build (even with daisy).
> 
> its not specific to gcc 4.9, however thats where I discovered it. The
> fix although is generic and should work
> in any compiler.

I'm already testing it with daisy build to fix one world build issue, if
that works, can we drop 4.9 from commit message?

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

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

  reply	other threads:[~2014-05-05  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140504111629.5E32A504E8@opal.openembedded.org>
2014-05-04 14:50 ` [oe-commits] Khem Raj : lttng-modules_2.3.3.bb: Fix build on ARM/gcc-4.9 Martin Jansa
2014-05-04 23:53   ` Khem Raj
2014-05-05  1:04     ` Martin Jansa [this message]
2014-05-05  1:04       ` Khem Raj

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=20140505010411.GJ2486@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox