All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] distcc_2.18.3.bb: Fix compilation on uclibc
Date: Sat, 21 May 2011 08:45:45 +0100	[thread overview]
Message-ID: <1305963945.18415.255.camel@lenovo.internal.reciva.com> (raw)
In-Reply-To: <51ED17D8-BCDC-4A28-B537-5EBDAE71772B@gmail.com>

On Sat, 2011-05-21 at 00:19 -0700, Khem Raj wrote:
> >> -EXTRA_OECONF = " --with-gtk "
> >> -
> >> +EXTRA_OECONF_libc-glibc = " --with-gtk "
> >> +EXTRA_OECONF_libc-uclibc = " --without-gtk --without-gnome "
> > 
> > Can you make this use the same logic as above?
> > 
> 
> Is there a problem with this logic ?

Not functionally but, if the DEPENDS are expressed in terms of a default
and then an override for uclibc, it seems like it would be natural for
the corresponding EXTRA_OECONF to be written the same way.

p.





  reply	other threads:[~2011-05-21  7:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 23:19 [PATCH 0/2] Opkg and distcc fix Khem Raj
2011-05-20 23:19 ` [PATCH 1/2] opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS} Khem Raj
2011-05-20 23:30   ` Saul Wold
2011-05-21  0:41     ` Khem Raj
2011-05-21  8:00   ` Phil Blundell
2011-05-21 23:04     ` Khem Raj
2011-05-20 23:19 ` [PATCH 2/2] distcc_2.18.3.bb: Fix compilation on uclibc Khem Raj
2011-05-20 23:31   ` Richard Purdie
2011-05-21  0:43     ` Khem Raj
2011-05-21  0:48     ` Khem Raj
2011-05-21  6:23   ` Koen Kooi
2011-05-21  6:34   ` Phil Blundell
2011-05-21  7:19     ` Khem Raj
2011-05-21  7:45       ` Phil Blundell [this message]
2011-05-21 19:17       ` Koen Kooi
2011-05-21 23:03         ` Khem Raj
2011-05-23 19:09 ` [PATCH 0/2] Opkg and distcc fix Saul Wold

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=1305963945.18415.255.camel@lenovo.internal.reciva.com \
    --to=pb@pbcl.net \
    --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.