On 30.06.2016 02:29, John Paul Adrian Glaubitz wrote:
Hello!
Attaching an updated patch which includes an additional alignment fix for m68k
by Michael Karcher. He discovered that "sem_t" was incorrectly aligned to 16
bits
which resulted in "create_db" crashing with [1]:
sh -x -c "lockfile -1 ../gen/firebird/bin/build-db.lock &&
../gen/firebird/bin/create_db empty.fdb; res=\$?; rm -f ../gen/firebird/bin/build-db.lock; exit
\$res"
+ lockfile -1 ../gen/firebird/bin/build-db.lock
+ ../gen/firebird/bin/create_db empty.fdb
The futex facility returned an unexpected error code.Aborted
+ res=134
+ rm -f ../gen/firebird/bin/build-db.lock
+ exit 134
../gen/Makefile.refDatabases:66: recipe for target 'empty.fdb' failed
This updated patch fixes this issue. However, firebird2.5 continues to FTBFS on
m68k [2]:
+ ../gen/firebird/bin/isql_static -i ../src/msgs/msg.sql msg.fdb
can't format message 17:0 -- message file
/usr/lib/m68k-linux-gnu/firebird/2.5/firebird.msg not found
Dynamic SQL Error
-SQL error code = -104
-Unexpected end of command - line 1, column 18
can't format message 17:120 -- message file
/usr/lib/m68k-linux-gnu/firebird/2.5/firebird.msg not found
can't format message 17:0 -- message file
/usr/lib/m68k-linux-gnu/firebird/2.5/firebird.msg not found
Adrian
This turns out to be a problem of the build environment. Firebird
creates its own btyacc (I did not yet verify whether Debian's btyacc has
the same problem), which creates a broken parser inside qemu, but the
same binary creates a correct parser when run in aranym, so the current
build problem is very likely a bug in the qemu version used on that
build host.
qemu on that host is built directly from the current upstream git
revision, it is not an installed debian package.
Best regards,
Michael Karcher