From: Helmut Grohne <helmut@subdivi.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Bastian Germann <bage@debian.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] debian: Fix FTCBFS: Skip crc32 test (Closes: #999879)
Date: Sat, 20 Nov 2021 08:32:40 +0100 [thread overview]
Message-ID: <YZikmB1aLZUX8FC7@alf.mars> (raw)
In-Reply-To: <20211119231105.GA449541@dread.disaster.area>
Hi Dave,
On Sat, Nov 20, 2021 at 10:11:05AM +1100, Dave Chinner wrote:
> I don't get it. The crcselftest does not use liburcu in
> any way, nor does it try to link against liburcu, so it should not
> fail because other parts of xfsprogs use liburcu.
>
> What's the build error that occurs?
As the build log shows, that's not technically accurate. You can find
logs of test builds for various architecture combinations at
http://crossqa.debian.net/src/xfsprogs. This is also available as a link
called "cross" in https://tracker.debian.org/xfsprogs.
The relevant part is:
| [TEST] CRC32
| In file included from crc32.c:35:
| ../include/platform_defs.h:27:10: fatal error: urcu.h: No such file or directory
| 27 | #include <urcu.h>
| | ^~~~~~~~
| compilation terminated.
I failed to figure a good way of dropping either include directive.
> We need to fix the generic cross-build problem in the xfsprogs code,
> not slap a distro-specific build band-aid over it.
I fully agree with this in principle. However, when I fail to find that
upstreamable solution, I try to at least provide a Debian-specific
solution to iterate from.
Can you propose a way to drop either #include?
Helmut
next prev parent reply other threads:[~2021-11-20 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 17:12 [PATCH 0/2] debian: Fix xfsprogs FT(C)BFS Bastian Germann
2021-11-19 17:12 ` [PATCH 1/2] debian: Generate .gitcensus instead of .census (Closes: #999743) Bastian Germann
2021-11-23 20:01 ` Bastian Germann
2021-11-23 20:08 ` Darrick J. Wong
2021-11-19 17:12 ` [PATCH 2/2] debian: Fix FTCBFS: Skip crc32 test (Closes: #999879) Bastian Germann
2021-11-19 23:11 ` Dave Chinner
2021-11-20 7:32 ` Helmut Grohne [this message]
2021-11-20 17:15 ` Darrick J. Wong
2021-11-20 22:20 ` Dave Chinner
2021-11-20 22:27 ` Dave Chinner
2021-11-22 23:32 ` Darrick J. Wong
2021-11-22 23:31 ` Darrick J. Wong
2021-11-22 23:37 ` Dave Chinner
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=YZikmB1aLZUX8FC7@alf.mars \
--to=helmut@subdivi.de \
--cc=bage@debian.org \
--cc=david@fromorbit.com \
--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).