-=| Cyril Brulebois, Mon, Jan 18, 2010 at 10:45:33PM +0100 |=- > Package: src:firebird2.5 > Version: 2.5.0.25784~ReleaseCandidate1.ds2-4 > Severity: serious > Justification: FTBFS > User: debian-...@lists.debian.org > Usertags: kfreebsd > > Hi, > > your package FTBFS on kfreebsd-* in experimental: > | make[4]: Entering directory > `/build/buildd-firebird2.5_2.5.0.25784~ReleaseCandidate1.ds2-4-kfreebsd-i386-7CJaH9/firebird2.5-2.5.0.25784~ReleaseCandidate1.ds2/gen' > | make[4]: `../gen/firebird/bin/create_db' is up to date. > | make[4]: Leaving directory > `/build/buildd-firebird2.5_2.5.0.25784~ReleaseCandidate1.ds2-4-kfreebsd-i386-7CJaH9/firebird2.5-2.5.0.25784~ReleaseCandidate1.ds2/gen' > | rm -f empty.fdb > | ../gen/firebird/bin/create_db empty.fdb > | ConfigStorage: mutex init error, status = 78 > | make[3]: *** [empty.fdb] Segmentation fault
The real error is "ConfigStorage: mutex init error, status = 78". After some digging, 78 appears to be a freebsd-specific error code, meaning 'not implemented' (ENOSYS) and is returned by a function that is supposed to initialize semaphores. (I guess the segmentation fault is because of the attempt of the code to handle the error by calling exit) > Full build logs at the usual place: > https://buildd.debian.org/status/package.php?suite=unstable&p=firebird2.5 I wonder if FreeBSD should define USE_SYS5SEMAPHORE the same way DARWIN does (line 37 of jrd/isc.h).
signature.asc
Description: Digital signature
