From: "zhangyi (F)" <yi.zhang@huawei.com>
To: cgxu519@mykernel.net
Cc: linux-unionfs <linux-unionfs@vger.kernel.org>
Subject: Re: Compile error of fsck.overlay on Fedora30
Date: Thu, 31 Oct 2019 22:20:45 +0800 [thread overview]
Message-ID: <0827d20f-6494-58b9-db2b-6536af803774@huawei.com> (raw)
In-Reply-To: <16e222490fd.db7c32a41966.5777637250125026331@mykernel.net>
Hi Chengguang,
Thanks for reporting, I will check and fix this soon.
Thanks,
Yi.
On 2019/10/31 22:07, Chengguang Xu Wrote:
> Hi Zhangyi,
>
> I found a compile error of fsck.overlay on my laptop(fedora 30), it looks like lacking of header in the check.c.
> After manually added <sys/sysmacros.h> compile succeeded without error.
>
> Detail info of compile error as below:
>
> [cgxu@localhost overlayfs-progs]$ make
> gcc -Wall -g -c fsck.c
> gcc -Wall -g -c common.c
> gcc -Wall -g -c lib.c
> gcc -Wall -g -c check.c
> check.c: In function ‘ovl_create_whiteout’:
> check.c:173:55: warning: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration]
> 173 | if (mknodat(dirfd, pathname, S_IFCHR | WHITEOUT_MOD, makedev(0, 0))) {
> | ^~~~~~~
> gcc -Wall -g -c mount.c
> gcc -Wall -g -c path.c
> gcc -Wall -g -c overlayfs.c
> gcc -lm fsck.o common.o lib.o check.o mount.o path.o overlayfs.o -o fsck.overlay
> /usr/bin/ld: check.o: in function `ovl_create_whiteout':
> /home/cgxu/git/overlayfs-progs/check.c:173: undefined reference to `makedev'
> collect2: error: ld returned 1 exit status
> make: *** [Makefile:10: overlay] Error 1
>
>
> Thanks,
> Chengguang
>
>
>
> .
>
prev parent reply other threads:[~2019-10-31 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:07 Compile error of fsck.overlay on Fedora30 Chengguang Xu
2019-10-31 14:20 ` zhangyi (F) [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=0827d20f-6494-58b9-db2b-6536af803774@huawei.com \
--to=yi.zhang@huawei.com \
--cc=cgxu519@mykernel.net \
--cc=linux-unionfs@vger.kernel.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