Bug#633402: aspectc++: FTBFS (kfreebsd): deeper syncronization trouble?
AspectC++ fails to build in parallel on kFreeBSD due to a corrupted file which is accessed concurrently during build. Reinhard told me hs traced it down to some [0] non-functional syncronization primitive. ... [0] Forgot the name again I'm horribly bad at remembering those shortened C identifiers. ... maybe we have some problem in glibc here? Do you have a test case ? The current gcc is more agressive in reordering, may be we miss some clobber in inline asm somewhere. Petr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633402: aspectc++: FTBFS (kfreebsd): deeper syncronization trouble?
Package: src: Version: Severity: normal Tags: sid wheezy Hi! AspectC++ fails to build in parallel on kFreeBSD due to a corrupted file which is accessed concurrently during build. Reinhard told me hs traced it down to some [0] non-functional syncronization primitive. Relating to the llvm problem, where the testsuite hung when running in parallel and the hang in python2.6 and python2.7 test suite that runs parallelization related stuff made me think whether it's a more general problem -- maybe we have some problem in glibc here? Filling as a aspectc++ bug as aspectc++ is definitely affected and putting debian-bsd@ in debbugs-cc in hope someone finds time to investigate. Full build log at https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2Barch=kfreebsd-amd64ver=1%3A1.0-4stamp=1309539673 Regards Christoph [0] Forgot the name again I'm horribly bad at remembering those shortened C identifiers. -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
