From: Adrian Bunk <bunk@stusta.de>
To: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] libowfat: upgrade 0.31 -> 0.32
Date: Wed, 30 Oct 2019 23:52:35 +0200 [thread overview]
Message-ID: <20191030215235.GA7373@localhost> (raw)
In-Reply-To: <1572468965-36724-1-git-send-email-zhengrq.fnst@cn.fujitsu.com>
This breaks the build of ncp:
| ncp.c:8:10: fatal error: dns.h: No such file or directory
| 8 | #include "dns.h"
| | ^~~~~~~
The reason is the following upstream change:
move headers to <libowfat/> upon install
The recipe was already doing this, so now we got
the header files in /usr/include/libowfat/libowfat
Fix in the libowfat recipe:
do_install() {
make install \
DESTDIR=${D} \
- INCLUDEDIR=${includedir}/${BPN} \
+ INCLUDEDIR=${includedir} \
LIBDIR=${libdir} \
MAN3DIR=${mandir}/man3
}
:
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-10-30 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:56 [meta-networking][PATCH] libowfat: upgrade 0.31 -> 0.32 Zheng Ruoqin
2019-10-30 21:52 ` Adrian Bunk [this message]
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=20191030215235.GA7373@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=zhengrq.fnst@cn.fujitsu.com \
/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.