From: Pavel Machek <pavel@ucw.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kernel list <linux-kernel@vger.kernel.org>,
jaegeuk@kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net,
Qiuyang Sun <sunqiuyang@huawei.com>
Subject: Re: Next 20190621: fails to link f2fs in x86-32
Date: Fri, 28 Jun 2019 12:10:50 +0200 [thread overview]
Message-ID: <20190628101050.GA7745@amd> (raw)
In-Reply-To: <20190624101844.50e4c4ff@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On Mon 2019-06-24 10:20:52, Stephen Rothwell wrote:
> Hi all,
>
> On Sat, 22 Jun 2019 19:49:45 +0200 Pavel Machek <pavel@ucw.cz> wrote:
> >
> > ld: fs/f2fs/gc.o: in function `f2fs_resize_fs':
> > gc.c:(.text+0x3a91): undefined reference to `__umoddi3'
> > ld: gc.c:(.text+0x3b70): undefined reference to `__udivdi3'
> > make: *** [Makefile:1052: vmlinux] Error 1
>
> This should be fixed in today's linux-next.
Thanks, I tested 5.2.0-rc6-next-20190627+ and that seems to work here.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2019-06-28 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:03 Next 20190620: fails to compile in netfilter on x86-32 Pavel Machek
2019-06-21 11:46 ` Stephen Rothwell
2019-06-22 17:49 ` Next 20190621: fails to link f2fs in x86-32 Pavel Machek
2019-06-22 17:51 ` Pavel Machek
2019-06-24 0:20 ` Stephen Rothwell
2019-06-28 10:10 ` Pavel Machek [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=20190628101050.GA7745@amd \
--to=pavel@ucw.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sunqiuyang@huawei.com \
--cc=yuchao0@huawei.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 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.