From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 205967] New: [bisected] f2fs compression support breaks build
Date: Wed, 25 Dec 2019 12:18:07 +0000 [thread overview]
Message-ID: <bug-205967-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205967
Bug ID: 205967
Summary: [bisected] f2fs compression support breaks build
Product: File System
Version: 2.5
Kernel Version: 5.5.0-rc2-next
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: david@ixit.cz
Regression: No
commit: 25d18e19a91e60837d36368ee939db13fd16dc64
breaks build for me (armv6):
/usr/bin/armv6-alpine-linux-musleabihf-ld: fs/f2fs/file.o: in function
`f2fs_truncate_blocks':
/mnt/linux/.output/../fs/f2fs/file.c:738: undefined reference to
`__aeabi_uldivmod'
make[1]: *** [/mnt/linux/Makefile:1079: vmlinux] Error 1
and Pavel Machek (x86-32) [1]:
LD .tmp_vmlinux1
ld: fs/f2fs/file.o: in function `f2fs_truncate_blocks':
file.c:(.text+0x2968): undefined reference to `__udivdi3'
make: *** [Makefile:1079: vmlinux] Error 1
[1] https://lkml.org/lkml/fancy/2019/12/22/48
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2019-12-25 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 12:18 bugzilla-daemon [this message]
2019-12-26 1:40 ` [f2fs-dev] [Bug 205967] [bisected] f2fs compression support breaks build bugzilla-daemon
2020-01-01 22:45 ` bugzilla-daemon
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=bug-205967-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.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 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).