This queue is for tickets about the IO-AIO CPAN distribution.

Report information
The Basics

Nobody in particular
fraserbn [...]

(no value)
Broken in:
Fixed in:
(no value)


Subject: Compilation error with musl
This prevents IO::AIO from compiling in alpine images, which use musl C. The attached patch just ends the existing workaround for musl to one more location.
Subject: 0001-Yet-another-fix-for-musl-FS_IOC_FIEMAP.patch
From fbf60075e506965450c52e48b9fce1557205664c Mon Sep 17 00:00:00 2001 From: Brian Fraser <> Date: Thu, 26 Nov 2020 19:35:27 +0100 Subject: [PATCH] Yet another fix for musl & FS_IOC_FIEMAP Just an extension of the existing workaround; fixes this compilation error on Alpine, which uses musl: AIO.xs: In function 'boot_IO__AIO': AIO.xs:1220:15: error: invalid application of 'sizeof' to incomplete type 'struct fiemap' 1220 | const_iv (FS_IOC_FIEMAP) | ^~~~~~~~~~~~~ AIO.xs:1099:42: note: in definition of macro 'const_iv' 1099 | # define const_iv(name) { # name, (IV) name }, --- AIO.xs | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AIO.xs b/AIO.xs index 914199f..2b0c3d3 100644 --- a/AIO.xs +++ b/AIO.xs @@ -1217,7 +1217,9 @@ BOOT: const_iv (FS_IOC_SETFLAGS) const_iv (FS_IOC_GETVERSION) const_iv (FS_IOC_SETVERSION) +# if __linux__ && (defined __GLIBC__ || defined __UCLIBC__) && defined(FS_IOC_FIEMAP) const_iv (FS_IOC_FIEMAP) +# endif const_iv (FS_IOC_FSGETXATTR) const_iv (FS_IOC_FSSETXATTR) const_iv (FS_IOC_SET_ENCRYPTION_POLICY) -- 2.29.2
Subject: Re: [ #133815] Compilation error with musl
Date: Fri, 27 Nov 2020 00:23:05 +0100
To: Brian Fraser via RT <>
From: Marc Lehmann <>
Hi! Please send your bug report to the official contact/author address for the module in question (or send it to, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with's bugs). Still, for some people, is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of didn't make their "service" optional - you can neither opt-in nor opt-out of as a module author. Just like a spammer, forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects and maybe similar services. (Many people confuse with for some reason). 2. It doesn't even work (there are still links to displayed). 3. Even if does no longer display the link, it doesn't actually affect (and tests have shown that people go to regardless) Even *iff* would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <> Last updated: 2012-04-22

This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with to