From: marius p. <ma...@gm...> - 2008-04-09 05:54:21
|
at the bottom of the page there is an ppc port mention that is already done and the page should be changed http://www.firebirdsql.org/index.php?op=devel&sub=engine and this page shoud be removed http://www.firebirdsql.org/index.php?op=devel&sub=engine&id=plat_ppc64 the tips can be used for other ports In general, porting Firebird to Linux/***64/***32 platform will not be difficult. - You need to register the new architecture in the build system and in a couple of places in the source code and make sure it builds properly. This is a good test by itself, as Firebird uses itself extensively during the build process. - Then you need to run QMDB and TCS tests<http://www.firebirdsql.org/index.php?op=devel&sub=qa&id=qmtest_howto>and make sure there are no new regressions. Alignment failures, a.k.a. SIGBUS errors, are the most likely problems you'll need to take care of. also the porting will be changed from what i have seen on devel list an example for arm port (it's just an sample not the final port) http://git.debian.org/?p=pkg-firebird/2.1.git;a=blob;f=debian/patches/port-arm.patch;h=2e161ba5155e0f43d34fc199b68db8dfa5ddab74;hb=HEAD and here is another port already included in the cvs head (Mips/mipsel) http://git.debian.org/?p=pkg-firebird/2.0.git;a=blob;f=debian/patches/port-mipsel.patch;h=0f99cab4278467c21347b727b806f47b80bc6ebf;hb=03bf3f72d00ad9da6d705a28fa26eef1cb306eed -- developer flamerobin.org |