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/2] groff: Fix sstate relocation issue
Date: Mon, 05 Sep 2011 17:48:18 +0100 [thread overview]
Message-ID: <1315241298.1243.1.camel@ted> (raw)
In-Reply-To: <1315159086.2896.0.camel@lenovo.internal.reciva.com>
On Sun, 2011-09-04 at 18:58 +0100, Phil Blundell wrote:
> On Sat, 2011-09-03 at 21:19 -0700, Saul Wold wrote:
> > + create_cmdline_wrapper ${D}/${bindir}/groff \
> > + -F${STAGING_DIR_NATIVE}/usr/share/groff/${PV}/font \
> > + -M${STAGING_DIR_NATIVE}/usr/share/groff/${PV}/tmac
> > +}
>
> Shouldn't that be ${datadir}?
or datadir_native :)
I'll pull and amend the patch with that change.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-05 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 4:19 [PATCH 0/2] sstate relocation patches Saul Wold
2011-09-04 4:19 ` [PATCH 1/2] groff: Fix sstate relocation issue Saul Wold
2011-09-04 17:58 ` Phil Blundell
2011-09-05 16:48 ` Richard Purdie [this message]
2011-09-04 4:19 ` [PATCH 2/2] opensp: " Saul Wold
2011-09-06 3:55 ` 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=1315241298.1243.1.camel@ted \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox