All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] pcmciautils: Upgrade 017 -> 018
Date: Thu, 21 Apr 2011 20:28:04 +0100	[thread overview]
Message-ID: <1303414084.5518.363.camel@rex> (raw)
In-Reply-To: <9efd8eca294cb7e3206e47e3b9bea503f3c87ac8.1303412254.git.raj.khem@gmail.com>

On Thu, 2011-04-21 at 11:59 -0700, Khem Raj wrote:
> version workaround is done in recipe itself
> by adding PV to CFLAGS
> 
> Since we define LIBC and pcmciutils use it too
> which hinders build when we define LIBC in
> environment. Its not used in the builds anyway
> so we get rid of depending on it

Why are you defining LIBC in the environment? That sounds like a
seriously bad idea. Our current environment handling should stop it
leaking into a build anyway shouldn't it?

Cheers,

Richard





  reply	other threads:[~2011-04-21 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 18:59 [PATCH 0/1] Upgrade pcmciautils 017 -> 018 Khem Raj
2011-04-21 18:59 ` [PATCH 1/1] pcmciautils: Upgrade " Khem Raj
2011-04-21 19:28   ` Richard Purdie [this message]
2011-04-21 19:48     ` Koen Kooi

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=1303414084.5518.363.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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.