linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 12 May 2020 23:00:13 +0900	[thread overview]
Message-ID: <CAK7LNAQ-=A0nDZK0FTzgJ6oJ-VbV33F1rVjvBAWgybSsUXaPVA@mail.gmail.com> (raw)
In-Reply-To: <20200512195712.690f02bb@canb.auug.org.au>

On Tue, May 12, 2020 at 6:57 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the fsinfo tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> /usr/lib/gcc-cross/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/ld: cannot find /usr/lib/x86_64-linux-gnu/libm-2.30.a
> /usr/lib/gcc-cross/x86_64-linux-gnu/9/../../../../x86_64-linux-gnu/bin/ld: cannot find /usr/lib/x86_64-linux-gnu/libmvec.a
>
> I don't know if this is a quirk of the build system or Debian's cross
> compiler setup.  Both those files exist in /usr/x86_64-linux-gnu/lib/.
>
> Masahiro, any thoughts?
>
> I have disabled the building of test_fsinfo for now:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 12 May 2020 19:49:33 +1000
> Subject: [PATCH] disable building fo test-fsinfo for now
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  samples/vfs/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/samples/vfs/Makefile b/samples/vfs/Makefile
> index f5bc5dfdf045..97e54c8be358 100644
> --- a/samples/vfs/Makefile
> +++ b/samples/vfs/Makefile
> @@ -1,5 +1,5 @@
>  # SPDX-License-Identifier: GPL-2.0-only
> -userprogs := test-fsinfo test-fsmount test-mntinfo test-statx
> +userprogs := test-fsmount test-mntinfo test-statx
>  always-y := $(userprogs)
>
>  userccflags += -I usr/include
> --
> 2.26.2
>
> --
> Cheers,
> Stephen Rothwell


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




David,

BTW, why is '-static' needed here?




--
Best Regards
Masahiro Yamada

  reply	other threads:[~2020-05-12 14:01 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 [this message]
2020-05-12 14:14   ` Stephen Rothwell
2020-05-12 23:18 ` David Howells
2020-05-12 23:26 ` David Howells
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='CAK7LNAQ-=A0nDZK0FTzgJ6oJ-VbV33F1rVjvBAWgybSsUXaPVA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).