linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@redhat.com>
To: Li GuiFu <bluce.lee@aliyun.com>
Cc: linux-erofs@lists.ozlabs.org, Shung Wang <waterbird0806@gmail.com>
Subject: Re: [PATCH v2] erofs-utils: support selinux file contexts
Date: Sun, 7 Jun 2020 17:51:28 +0800	[thread overview]
Message-ID: <20200607095128.GA6501@xiangao.remote.csb> (raw)
In-Reply-To: <0095f9b2-e999-e047-c789-b8ef6c1cea81@aliyun.com>

Hi Guifu,

On Sun, Jun 07, 2020 at 05:25:12PM +0800, Li GuiFu wrote:
> It cacuses one build error in my Ubuntu 18.04.1 LTS
> and it seems selinux static lib link cause it
> libtool: link: gcc -Wall -Werror -I../include -g -O2 -static -o
> mkfs.erofs mkfs_erofs-main.o  ../lib/.libs/liberofs.a
> -L/home/liguifu/codes/lz4 -luuid -lselinux -llz4
> /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libselinux.a(seusers.o):
> In function `getseuserbyname':
> (.text+0x5e9): warning: Using 'getgrouplist' in statically linked
> applications requires at runtime the shared libraries from the glibc
> version used for linking

Did you apply the following patch as well?
https://lore.kernel.org/r/20200531034510.5019-1-hsiangkao@aol.com/

And then I think you need "make distclean", "./autogen.sh" and
"./configure" again.

Thanks,
Gao Xiang


  reply	other threads:[~2020-06-07  9:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-30 16:11 [PATCH] erofs-utils: support selinux file contexts Gao Xiang
     [not found] ` <fb53174b-605c-b893-a2b0-d5a76132e244@aliyun.com>
2020-06-04  1:36   ` Gao Xiang
2020-06-06  8:17 ` [PATCH v2] " Gao Xiang
2020-06-07  9:25   ` Li GuiFu via Linux-erofs
2020-06-07  9:51     ` Gao Xiang [this message]
2020-06-07 11:49   ` Li GuiFu via Linux-erofs
2020-06-07 14:07     ` Gao Xiang
2020-06-07 14:59   ` Li Guifu
2020-06-08 12:34   ` [PATCH v3] " Gao Xiang via Linux-erofs
2020-06-08 13:08     ` [PATCH v4] " Gao Xiang via Linux-erofs
2020-06-08 15:51       ` Li GuiFu via Linux-erofs

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=20200607095128.GA6501@xiangao.remote.csb \
    --to=hsiangkao@redhat.com \
    --cc=bluce.lee@aliyun.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=waterbird0806@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).