From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Julian Wollrath <jwollrath@web.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: v4.12-rc1 does not compile: xfs_file_iomap_begin/end undefined reference
Date: Thu, 18 May 2017 10:27:01 -0700 [thread overview]
Message-ID: <20170518172701.GB4519@birch.djwong.org> (raw)
In-Reply-To: <20170518191605.33635584@saldaea>
On Thu, May 18, 2017 at 07:16:05PM +0200, Julian Wollrath wrote:
> Hi,
>
> v4.12-rc1 does not compile with the attached config. I get the
> following:
> fs/built-in.o: In function `xfs_file_iomap_end':
> xfs_iomap.c:(.text+0xb7f75): undefined reference to `put_dax'
> fs/built-in.o: In function `xfs_file_iomap_begin':
> xfs_iomap.c:(.text+0xb8802): undefined reference to `dax_get_by_host
Does the patch referenced in
https://marc.info/?l=linux-xfs&m=149493347832378&w=2
fix this too?
--D
>
> with the following diff I do not get the error:
> --- .config.old 2017-05-18 17:45:44.621011682 +0200
> +++ .config 2017-05-18 19:06:56.608813894 +0200
> @@ -3362,7 +3362,7 @@ CONFIG_RAS=y
> #
> # CONFIG_ANDROID is not set
> # CONFIG_LIBNVDIMM is not set
> -CONFIG_DAX=m
> +CONFIG_DAX=y
> # CONFIG_DEV_DAX is not set
> # CONFIG_NVMEM is not set
> # CONFIG_STM is not set
> @@ -3439,7 +3439,7 @@ CONFIG_XFS_POSIX_ACL=y
> # CONFIG_BTRFS_FS is not set
> # CONFIG_NILFS2_FS is not set
> # CONFIG_F2FS_FS is not set
> -# CONFIG_FS_DAX is not set
> +CONFIG_FS_DAX=y
> CONFIG_FS_POSIX_ACL=y
> CONFIG_EXPORTFS=y
> # CONFIG_EXPORTFS_BLOCK_OPS is not set
>
> So I guess, there is some dependency on that option missing.
>
>
> Best regards,
> Julian Wollrath
>
> --
> () ascii ribbon campaign - against html e-mail
> /\ - against proprietary attachments
next prev parent reply other threads:[~2017-05-18 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 17:16 v4.12-rc1 does not compile: xfs_file_iomap_begin/end undefined reference Julian Wollrath
2017-05-18 17:27 ` Darrick J. Wong [this message]
2017-05-18 17:53 ` Julian Wollrath
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=20170518172701.GB4519@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=jwollrath@web.de \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).