Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@redhat.com>
To: nl6720 <nl6720@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: Cannot build erofs-utils 1.2: multiple definition of `sbi'
Date: Tue, 8 Dec 2020 18:46:26 +0800	[thread overview]
Message-ID: <20201208104626.GA3140556@xiangao.remote.csb> (raw)
In-Reply-To: <10789285.Na0ui7I3VY@walnut>

Hi nl6720,

On Tue, Dec 08, 2020 at 12:35:42PM +0200, nl6720 wrote:
> Hi,
> 
> I'm having trouble building erofs-utils 1.2. It fails in "Making all in mkfs":
> 
> /bin/sh ../libtool  --tag=CC   --mode=link gcc -Wall -Werror -I../include -march=x86-64 -mtune=generic -O2 -pipe -fno-plt  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -o mkfs.erofs mkfs_erofs-main.o -luuid  ../lib/liberofs.la  -R/usr/lib -llz4 
> libtool: link: gcc -Wall -Werror -I../include -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now -o mkfs.erofs mkfs_erofs-main.o  -luuid ../lib/.libs/liberofs.a -llz4 -Wl,-rpath -Wl,/usr/lib
> /usr/bin/ld: ../lib/.libs/liberofs.a(liberofs_la-inode.o):(.bss+0x40000): multiple definition of `sbi'; ../lib/.libs/liberofs.a(liberofs_la-super.o):(.bss+0x0): first defined here
> 
> This is on Arch Linux with:
> binutils 2.35.1-1
> gcc 10.2.0-4
> libtool 2.4.6+42+gb88cebd5-14

Thanks for the quick feedback! since inode.o is for just mkfs, and super.o is for just erofsfuse,
so I didn't observe such issue before with my configuration... I think it may need a
temporary fix for packaging (if erofsfuse is unneeded, since lz4-1.9.3 is needed safely,
is just get rid of the one in lib/super.c, or move these two into lib/config.c....)
I will submit a formal submission later....

Thanks,
Gao Xiang


      reply	other threads:[~2020-12-08 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 10:35 Cannot build erofs-utils 1.2: multiple definition of `sbi' nl6720
2020-12-08 10:46 ` Gao Xiang [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=20201208104626.GA3140556@xiangao.remote.csb \
    --to=hsiangkao@redhat.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=nl6720@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