Red Hat Bugzilla – Bug 715799
Last modified: 2011-07-22 00:21:33 EDT
ghc-hinotify-0.3.1-9.fc16.src.rpm Failed To Build From Source against the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more information.
If you believe this is actually a bug in another package, do NOT change the component in this bug or close this bug. Instead, add the appropriate bug number from the other package to the "Depends on" line in this bug. If the other package does not yet have a bug created that you think matches, please create one. Doing so helps us properly track bugs and their dependencies, just as we track package dependencies. (If you close this bug, and the other package is not fixed before the next FTBFS run, a new bug will get created. Please follow the above advice to avoid such duplication.)
Created attachment 507203 [details]
root.log for x86_64
Created attachment 507204 [details]
build.log for x86_64
Created attachment 507205 [details]
mock.log for x86_64
*** Bug 715495 has been marked as a duplicate of this bug. ***
I tried building with ghc-7.0.4-26.fc16 on f15 and it built fine,
so this seems to be due to done other change in F16.
Off the top of my head I'd say the main suspects that
I can imagine are either the kernel or glibc perhaps.
Hm, "sys/inotify.h" is from glibc-headers at least.
But both it and linux/inotify.h look unchanged since f15.
Also gcc and cpp in f16 and f15 are same currently.
Updating f15 to latest rawhide kernel doesn't seem to make a difference either.
Ok it should have clicked a little earlier: asm => binutils.
Downgrading from binutils-188.8.131.52.1-5.fc16 to binutils-184.108.40.206.6-5.fc15 fixes the problem though.
Testing little more (I call it "binary bisecting"):
build is ok with binutils-220.127.116.11.6-2.fc16 but
breaks with binutils-18.104.22.168.7-1.fc16.
So I guess some upstream change in binutils between
22.214.171.124.6 and 126.96.36.199.7 is the cause of the problem.
Ah, I see: removing -fvia-C from hinotify.cabal makes it build again.
This might actually be a bug in the ghc C backend: see bug 717495.
Should be fixed with ghc-hinotify-0.3.1-11.fc16.