fts3token-3.3... Ok make: *** [test] Bus error Reproducible: Always
Created attachment 256864 [details] emerge --info =dev-db/sqlite-3.7.3
Created attachment 256865 [details] emerge -pqv =dev-db/sqlite-3.7.3
Created attachment 256866 [details] /var/tmp/portage/dev-db/sqlite-3.7.3/temp/build.log
Created attachment 256868 [details] /var/tmp/portage/dev-db/sqlite-3.7.3/temp/environment
Please report the problem to upstream. I don't have access to sparc hardware, so I can't help.
Alex, Please, try to reproduce the failure on latest sqlite. I see the following faults on sqlite-3.7.7.1/sparc32, none of them are alignment faults: Failures on these tests: e_expr-31.2.4 wal-18.2.3.1.5 wal-18.2.3.2.5 wal-18.2.3.3.5 wal-18.2.4.1.5 wal-18.2.4.2.5 wal-18.2.4.3.5 wal-18.2.5.1.5 wal-18.2.5.2.5 wal-18.2.5.3.5 wal-18.2.6.1.5 wal-18.2.6.2.5 wal-18.2.6.3.5 wal-18.2.7.1.5 wal-18.2.7.2.5 wal-18.2.7.3.5 wal-18.2.8.1.5 wal-18.2.8.2.5 wal-18.2.8.3.5 wal-18.2.9.1.5 wal-18.2.9.2.5 wal-18.2.9.3.5 wal-18.2.10.1.5 wal-18.2.10.2.5 wal-18.2.10.3.5 wal2-10.2.2 wal2-10.2.3 I see addressing of some alignment fixes in FTS3 source (fts3GetMatchinfo function). Thanks!
(In reply to comment #6) I got the same testresults for sqlite-3.7.7.1 on sparc. Without test enabled, the packages compiles fine. Are these test errors something for upstream btw? > > Failures on these tests: e_expr-31.2.4 wal-18.2.3.1.5 wal-18.2.3.2.5 > wal-18.2.3.3.5 wal-18.2.4.1.5 wal-18.2.4.2.5 wal-18.2.4.3.5 wal-18.2.5.1.5 > wal-18.2.5.2.5 wal-18.2.5.3.5 wal-18.2.6.1.5 wal-18.2.6.2.5 wal-18.2.6.3.5 > wal-18.2.7.1.5 wal-18.2.7.2.5 wal-18.2.7.3.5 wal-18.2.8.1.5 wal-18.2.8.2.5 > wal-18.2.8.3.5 wal-18.2.9.1.5 wal-18.2.9.2.5 wal-18.2.9.3.5 wal-18.2.10.1.5 > wal-18.2.10.2.5 wal-18.2.10.3.5 wal2-10.2.2 wal2-10.2.3 >
It might be wise to check with upstream on this indeed. I don't see an immediate ticket on their site for sparc or "bus error" notices in their test. https://www.sqlite.org/src/reportlist If you create an upstream ticket (best that you create it as you can reproduce and/or add/give more information if they need it) do give some feedback on it (the URL) here so we can also follow-up if needed.
Is this problem reproducible with dev-db/sqlite-3.11.0?