From: "Darrick J. Wong" <djwong@kernel.org>
To: "Páder Rezső" <rezso@rezso.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfsprogs build: missing hard dependency?
Date: Fri, 11 Oct 2024 09:38:14 -0700 [thread overview]
Message-ID: <20241011163814.GW21853@frogsfrogsfrogs> (raw)
In-Reply-To: <20241011141522.36415e20@rezso>
On Fri, Oct 11, 2024 at 02:15:22PM +0200, Páder Rezső wrote:
> Hello,
>
>
> I tried to compile now the xfsprogs 6.10.1 release, but it failed:
>
>
> /bin/ld: fsproperties.o: in function `fileio_to_fsprops_handle':
> /var/uhubuild/work/compile/io/fsproperties.c:63:(.text+0x155): undefined reference to `fsprops_open_handle'
> /bin/ld: fsproperties.o: in function `print_fsprop':
> /var/uhubuild/work/compile/io/fsproperties.c:99:(.text+0x26d): undefined reference to `fsprops_get'
> /bin/ld: fsproperties.o: in function `listfsprops_f':
> /var/uhubuild/work/compile/io/fsproperties.c:133:(.text+0x380): undefined reference to `fsprops_walk_names'
> /bin/ld: /var/uhubuild/work/compile/io/fsproperties.c:139:(.text+0x390): undefined reference to `fsprops_free_handle'
> /bin/ld: fsproperties.o: in function `removefsprops_f':
> /var/uhubuild/work/compile/io/fsproperties.c:331:(.text+0x48f): undefined reference to `fsprops_remove'
> /bin/ld: /var/uhubuild/work/compile/io/fsproperties.c:339:(.text+0x4a8): undefined reference to `fsprops_free_handle'
> /bin/ld: fsproperties.o: in function `getfsprops_f':
> /var/uhubuild/work/compile/io/fsproperties.c:189:(.text+0x5b6): undefined reference to `fsprops_get'
> /bin/ld: /var/uhubuild/work/compile/io/fsproperties.c:199:(.text+0x5e3): undefined reference to `fsprops_free_handle'
> /bin/ld: fsproperties.o: in function `setfsprops_f':
> /var/uhubuild/work/compile/io/fsproperties.c:271:(.text+0x6d4): undefined reference to `fsprops_set'
> /bin/ld: /var/uhubuild/work/compile/io/fsproperties.c:284:(.text+0x74f): undefined reference to `fsprops_free_handle'
> collect2: error: ld returned 1 exit status
>
> These functions are defined in libfrog/fsprops.h, but this is included
> only if the libattr is exists.
>
> After adding libattr to build dependencies, the build is succesful, so
> I think, the libattr always needed for this source.
I already removed the libattr dependencies:
https://lore.kernel.org/linux-xfs/172783101339.4035924.6880384393728950920.stgit@frogsfrogsfrogs/
(xfsprogs 6.11 will probably be out soonish...)
--D
> --
> Bestr regards.
>
> Rezso
>
prev parent reply other threads:[~2024-10-11 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 12:15 xfsprogs build: missing hard dependency? Páder Rezső
2024-10-11 16:38 ` Darrick J. Wong [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=20241011163814.GW21853@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rezso@rezso.net \
/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.