Hi, Am Montag, den 07.03.2011, 13:51 +0530 schrieb Joachim Breitner: > Strangely, on kfreebsd-i386 everything works fine. What is this > randomness? One difference according to the build logs is that the > failing build hat binutils_2.21-4 while the successful build had > binutils_2.21-3. The changelog for binutils_2.21-4 is: > * Fix handling of writable .eh_frame section in gold, taken from the > 2.21 branch. > which sounds unrelated. maybe it is related to libc (which, after all contains pthreads) and of which experimental has a newer version (2.13) than unstable (2.11). So here is a survey of all recent build logs. OK means no mention of the the sem_open build error, might have failed for other reasons g/ghc/7.0.1-1/amd64_1298874599_log.bz2 libc6-dev_2.13-0exp2 ghc6_6.12.3-1 OK g/ghc/7.0.1-1/armel_1298874619_log.bz2 libc6-dev_2.11.2-11 ghc6_6.12.1-13 NOT OK g/ghc/7.0.1-1/kfreebsd-amd64_1298854895_log.bz2 libc0.1-dev_2.11.2-11 ghc6_6.12.3-1 OK g/ghc/7.0.1-1/kfreebsd-i386_1298853856_log.bz2 libc0.1-dev_2.11.2-11 ghc6_6.12.3-1 OK g/ghc/7.0.1-1/mipsel_1299136864_log.bz2 libc6-dev_2.11.2-6 ghc6_6.12.1-13 OK g/ghc/7.0.1-1/powerpc_1298854095_log.bz2 libc6-dev_2.11.2-11 ghc6_6.12.3-1 OK g/ghc/7.0.1-1/s390_1298867048_log.bz2 libc6-dev_2.11.2-7 ghc6_6.12.1-13 OK g/ghc/7.0.1-1/sparc_1298866742_log.bz2 libc6-dev_2.11.2-11 ghc6_6.12.3-1 NOT OK g/ghc/7.0.2-1/i386_1299446001_log.bz2 libc6-dev_2.11.2-11 ghc_7.0.1-1 OK g/ghc/7.0.2-1/kfreebsd-amd64_1299357096_log.bz2 libc0.1-dev_2.11.2-11 ghc_7.0.1-1 OK g/ghc/7.0.2-1/kfreebsd-i386_1299355722_log.bz2 libc0.1-dev_2.13-0exp2 ghc_7.0.1-1 OK g/ghc/7.0.2-1/mipsel_1299383820_log.bz2 libc6-dev_2.11.2-11 ghc_7.0.1-1 OK g/ghc/7.0.2-1/powerpc_1299367262_log.bz2 libc6-dev_2.11.2-11 ghc6_6.12.1-13 OK g/ghc/7.0.2-1/s390_1299370097_log.bz2 libc6-dev_2.11.2-11 ghc_7.0.1-1 OK g/ghc/7.0.2-1/sparc_1299352729_log.bz2 libc6-dev_2.11.2-11 ghc6_6.12.1-13 NOT OK h/haskell-transformers/0.2.2.0-1/amd64_1299452539_log.bz2 libc6-dev_2.13-0exp3 ghc_7.0.2-1 OK h/haskell-transformers/0.2.2.0-1+b1/kfreebsd-amd64_1299445919_log.bz2 libc0.1-dev_2.13-0exp2 ghc_7.0.2-1 NOT OK h/haskell-transformers/0.2.2.0-1+b1/kfreebsd-i386_1299447371_log.bz2 libc0.1-dev_2.11.2-11 ghc_7.0.2-1 OK h/haskell-transformers/0.2.2.0-1/kfreebsd-amd64_1299334615_log.bz2 libc0.1-dev_2.11.2-11 ghc_7.0.1-1 OK h/haskell-transformers/0.2.2.0-1/kfreebsd-i386_1299333493_log.bz2 libc0.1-dev_2.11.2-11 ghc_7.0.1-1 OK h/haskell-transformers/0.2.2.0-1/mipsel_1299357345_log.bz2 libc6-dev_2.11.2-6 ghc_7.0.1-1 OK h/haskell-transformers/0.2.2.0-1/s390_1299468097_log.bz2 libc6-dev_2.11.2-11 ghc_7.0.2-1 OK h/haskell-mtl/2.0.1.0-1+b1/kfreebsd-i386_1299446150_log.bz2 libc0.1-dev_2.13-0exp2 ghc_7.0.1-1 OK h/haskell-mtl/2.0.1.0-1/kfreebsd-amd64_1299343188_log.bz2 libc0.1-dev_2.13-0exp2 ghc_7.0.1-1 NOT OK h/haskell-mtl/2.0.1.0-1/kfreebsd-i386_1299338369_log.bz2 libc0.1-dev_2.11.2-11 ghc_7.0.1-1 OK Hmm, is this useful? I don’t see a real pattern. We see failures with both versions of libc, with all four different versions of ghc available, across different architectures... Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part