All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] PUs for telepathy and gstreamer1.0
Date: Mon, 05 Aug 2013 15:13:43 +0100	[thread overview]
Message-ID: <3845418.BXzYRjkcFy@helios> (raw)
In-Reply-To: <CAJTo0LYTjnD32wbx2HUEQuXNiJGnjhZWYmQ3PGvfEaYjACr1fQ@mail.gmail.com>

On Monday 05 August 2013 12:45:02 Burton, Ross wrote:
> On 2 August 2013 16:39, Cristian Iorga <cristian.iorga@intel.com> wrote:
> > Cristian Iorga (7):
> >   telepathy-mission-control: upgrade to v5.15.0
> >   telepathy-idle: upgrade to v0.1.16
> >   gstreamer1.0: upgrade to v1.0.9
> >   gstreamer1.0-plugins-base: upgrade to v1.0.9
> >   gstreamer1.0-plugins-good: upgrade to v1.0.9
> >   gstreamer1.0-libav: upgrade to v1.0.9
> >   gstreamer1.0-plugins-bad: upgrade to v1.0.9
> 
> Build tested and verified buildhistory.
> 
> In another commit can you add an INSANE_SKIP for the text-rel warnings
> in gstreamer1.0-libav?  That's a known issue with libav afaik.

Are you sure about this? Coincidentally I have been looking at bringing in 
libav from meta-oe, and I can see in the configure script explicitly disables 
PIC for x86 (32-bit) but not other architectures, so I guess you'd need to 
append " textrel" to INSANE_SKIP only for i586, which is what I'm going to be 
doing there. However I'll admit I haven't done a build for another arch yet to 
check if the warnings are not present there.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      parent reply	other threads:[~2013-08-05 14:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 15:39 [PATCH 0/7] PUs for telepathy and gstreamer1.0 Cristian Iorga
2013-08-02 15:39 ` [PATCH 1/7] telepathy-mission-control: upgrade to v5.15.0 Cristian Iorga
2013-08-02 15:39 ` [PATCH 2/7] telepathy-idle: upgrade to v0.1.16 Cristian Iorga
2013-08-02 15:39 ` [PATCH 3/7] gstreamer1.0: upgrade to v1.0.9 Cristian Iorga
2013-08-02 15:39 ` [PATCH 4/7] gstreamer1.0-plugins-base: " Cristian Iorga
2013-08-02 15:39 ` [PATCH 5/7] gstreamer1.0-plugins-good: " Cristian Iorga
2013-08-02 15:39 ` [PATCH 6/7] gstreamer1.0-libav: " Cristian Iorga
2013-08-02 15:39 ` [PATCH 7/7] gstreamer1.0-plugins-bad: " Cristian Iorga
2013-08-05 11:45 ` [PATCH 0/7] PUs for telepathy and gstreamer1.0 Burton, Ross
2013-08-05 13:59   ` Iorga, Cristian
2013-08-05 14:13   ` Paul Eggleton [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=3845418.BXzYRjkcFy@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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.