From: Khem Raj <raj.khem@gmail.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] logrotate: obey our flags
Date: Mon, 25 Aug 2014 10:51:47 -0700 [thread overview]
Message-ID: <20140825175147.GB25050@haswell> (raw)
In-Reply-To: <CABcZAN=x7u=gF=-NfbBNLUcqvXgzte_CK_52rQGYikaNSXqU_A@mail.gmail.com>
On 14-08-25 10:21:31, Christopher Larson wrote:
> On Mon, Aug 25, 2014 at 10:19 AM, Khem Raj <raj.khem@gmail.com> wrote:
>
> > On 14-08-25 21:22:04, Fahad Usman wrote:
> > > Needed to quiet GNU_HASH warnings, amd some minor fixes.
> > >
> > > Signed-off-by: Fahad Usman <fahad.usman@gmail.com>
> > > Signed-off-by: Christopher Larson <kergoth@gmail.com>
> > > ---
> > > meta/recipes-extended/logrotate/logrotate_3.8.7.bb | 18
> > ++++++++++++++++--
> > > 1 file changed, 16 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/meta/recipes-extended/logrotate/logrotate_3.8.7.bb
> > b/meta/recipes-extended/logrotate/logrotate_3.8.7.bb
> > > index 3a6a228..42cd764 100644
> > > --- a/meta/recipes-extended/logrotate/logrotate_3.8.7.bb
> > > +++ b/meta/recipes-extended/logrotate/logrotate_3.8.7.bb
> > > @@ -16,7 +16,21 @@ SRC_URI = "
> > https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.g
> > > SRC_URI[md5sum] = "99e08503ef24c3e2e3ff74cc5f3be213"
> > > SRC_URI[sha256sum] =
> > "f6ba691f40e30e640efa2752c1f9499a3f9738257660994de70a45fe00d12b64"
> > >
> > > -EXTRA_OEMAKE = ""
> > > +# If RPM_OPT_FLAGS is unset, it adds -g itself rather than obeying our
> > > +# optimization variables, so use it rather than EXTRA_CFLAGS.
> > > +EXTRA_OEMAKE = "\
> > > + LFS= \
> > > + OS_NAME='${OS_NAME}' \
> > > + \
> > > + 'CC=${CC}' \
> >
> > hmmm CC may have spaces in it so you might need 'CC="${CC}"' or somesuch
>
>
> Nope, the whole CC=${CC} argument is already quoted, note the single quotes
> around it. Those quotes mean the entire CC=${CC} bit ends up in the
> appropriate argument for make, so there's no need to quote the value alone.
What happens inside makefile is what I am concerned
in case of python, IIRC it passed it but when CC was used it would
freak out since CC now was a multiword str but then those were not inside makefiles
if you have verified thats fine here then I am OK.
next prev parent reply other threads:[~2014-08-25 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 16:22 [PATCH 1/2] logrotate: obey our flags Fahad Usman
2014-08-25 16:22 ` [PATCH 2/2] logrotate: add packageconfigs Fahad Usman
2014-08-27 15:52 ` Burton, Ross
2014-08-27 16:19 ` Christopher Larson
2014-08-25 16:30 ` [PATCH 1/2] logrotate: obey our flags Christopher Larson
2014-08-25 17:19 ` Khem Raj
2014-08-25 17:21 ` Christopher Larson
2014-08-25 17:51 ` Khem Raj [this message]
2014-08-26 7:43 ` Usman, Fahad
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=20140825175147.GB25050@haswell \
--to=raj.khem@gmail.com \
--cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox