From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the fsinfo tree
Date: Wed, 13 May 2020 00:14:12 +1000 [thread overview]
Message-ID: <20200513001412.12598111@canb.auug.org.au> (raw)
In-Reply-To: <CAK7LNAQ-=A0nDZK0FTzgJ6oJ-VbV33F1rVjvBAWgybSsUXaPVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Hi Masahiro,
On Tue, 12 May 2020 23:00:13 +0900 Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> I also failed to build it, but the error message
> was different.
>
> The following worked for me at least.
> (Ubuntu 20.04).
>
> diff --git a/samples/vfs/Makefile b/samples/vfs/Makefile
> index 97e54c8be358..539fb3a56af3 100644
> --- a/samples/vfs/Makefile
> +++ b/samples/vfs/Makefile
> @@ -1,7 +1,8 @@
> # SPDX-License-Identifier: GPL-2.0-only
> -userprogs := test-fsmount test-mntinfo test-statx
> +userprogs := test-fsinfo test-fsmount test-mntinfo test-statx
> always-y := $(userprogs)
>
> userccflags += -I usr/include
>
> -test-fsinfo-userldflags += -static -lm
> +test-fsinfo-userldflags := -static
> +test-fsinfo-userldlibs := -lm
Thanks, I will change the merge resolution to that.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-12 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 9:57 linux-next: build failure after merge of the fsinfo tree Stephen Rothwell
2020-05-12 14:00 ` Masahiro Yamada
2020-05-12 14:14 ` Stephen Rothwell [this message]
2020-05-12 23:26 ` David Howells
2020-05-12 23:18 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2020-05-12 10:47 Stephen Rothwell
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=20200513001412.12598111@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@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