From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] xterm: use ${libdir} to avoid installed-vs-shipped error on ppc64
Date: Fri, 28 Oct 2016 13:32:37 -0200 [thread overview]
Message-ID: <CAP9ODKqgJE_15K6=4RcTzh34u6wNLKiK+w1hZ2LMz-mFTY9C0Q@mail.gmail.com> (raw)
In-Reply-To: <CABcZANnSmHOMkrKJ3M6CQN62+JHXCbRzXKZ3Ucx8PQ2_9cfmhQ@mail.gmail.com>
On Fri, Oct 28, 2016 at 1:07 PM, Christopher Larson <clarson@kergoth.com> wrote:
> On Fri, Oct 28, 2016 at 3:07 AM, <ting.liu@nxp.com> wrote:
>
>> xterm installs files into PREFIX/lib/X11/app-defaults by default.
>> This leads to QA issue on ppc64 which defines libdir as /usr/lib64:
>> ERROR: QA Issue: xterm: Files/directories were installed but not shipped
>> in any package:
>> /usr/lib
>> /usr/lib/X11
>> /usr/lib/X11/app-defaults
>> /usr/lib/X11/app-defaults/UXTerm
>> /usr/lib/X11/app-defaults/KOI8RXTerm-color
>> /usr/lib/X11/app-defaults/XTerm-color
>> /usr/lib/X11/app-defaults/UXTerm-color
>> /usr/lib/X11/app-defaults/KOI8RXTerm
>> /usr/lib/X11/app-defaults/XTerm
>>
>> Fix it by passing --with-app-defaults=${libdir}/X11/app-defaults to
>> configure.
>>
>> Signed-off-by: Ting Liu <ting.liu@nxp.com>
>> ---
>> meta-oe/recipes-graphics/xorg-app/xterm_325.bb | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta-oe/recipes-graphics/xorg-app/xterm_325.bb
>> b/meta-oe/recipes-graphics/xorg-app/xterm_325.bb
>> index e0baf3c..48556c7 100644
>> --- a/meta-oe/recipes-graphics/xorg-app/xterm_325.bb
>> +++ b/meta-oe/recipes-graphics/xorg-app/xterm_325.bb
>> @@ -14,6 +14,7 @@ PACKAGECONFIG[xft] = "--enable-freetype,--disable-freetype,libxft
>> fontconfig fre
>>
>> EXTRA_OECONF = " --x-includes=${STAGING_INCDIR} \
>> --x-libraries=${STAGING_LIBDIR} \
>> + --with-app-defaults=${libdir}/X11/app-defaults \
>> FREETYPE_CONFIG=${STAGING_BINDIR_CROSS}/freetype-config
>> \
>> --disable-imake \
>> --disable-rpath-hack \
>>
>
> Are you sure this is correct? I highly doubt those files are actually
> multilib specific. Would it not be better to just package these files in
> their current location?
Or use datadir
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2016-10-28 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 10:07 [meta-oe][PATCH] xterm: use ${libdir} to avoid installed-vs-shipped error on ppc64 ting.liu
2016-10-28 15:07 ` Christopher Larson
2016-10-28 15:32 ` Otavio Salvador [this message]
2016-10-31 4:15 ` Ting Liu
[not found] <1476803797-18279-1-git-send-email-ting.liu@nxp.com>
2016-10-18 15:24 ` Otavio Salvador
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='CAP9ODKqgJE_15K6=4RcTzh34u6wNLKiK+w1hZ2LMz-mFTY9C0Q@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=openembedded-devel@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.