All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-2.0: recommend shared-mime-info
Date: Wed, 13 Sep 2017 22:18:29 +0100	[thread overview]
Message-ID: <1505337509.18640.84.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAKmqyKMoTxxiQJ5jsCP9bHdNinEHG5mfb=fWUCaS+_6C+ZFY9A@mail.gmail.com>

On Wed, 2017-09-13 at 14:12 -0700, Alistair Francis wrote:
> On Wed, Sep 13, 2017 at 2:09 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Wed, 2017-09-13 at 13:55 -0700, Alistair Francis wrote:
> > > 
> > > On Wed, Sep 13, 2017 at 1:42 PM, Burton, Ross <ross.burton@intel.
> > > com>
> > > wrote:
> > > > 
> > > > 
> > > > Can you share a log showing that?
> > > This is the full log, so it's not just OpenSSL:
> > I suspect the new dependency means other things get built on mingw
> > which have never been needed until now. We may need to remove the
> > dependency for mingw to avoid this..
> Yeah, that is what I suspected. I tried the BAD_RECOMMENDATIONS in
> the
> mingw machine-sdk conf, but that didn't seem to work.

You want something like:

RRECOMMENDS_${PN}_remove_mingw32_pn-glib-2.0 = "shared-mime-info"

(I don't remember the exact mingw override offhand)

Cheers,

Richard



  reply	other threads:[~2017-09-13 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 15:08 [PATCH] glib-2.0: recommend shared-mime-info Ross Burton
2017-09-13 20:07 ` Alistair Francis
2017-09-13 20:42   ` Burton, Ross
2017-09-13 20:55     ` Alistair Francis
2017-09-13 21:09       ` Richard Purdie
2017-09-13 21:12         ` Alistair Francis
2017-09-13 21:18           ` Richard Purdie [this message]
2017-09-14 21:00             ` Alistair Francis

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=1505337509.18640.84.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alistair23@gmail.com \
    --cc=openembedded-core@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 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.