From: Damyan I. <da...@mo...> - 2006-10-14 20:58:53
Attachments:
signature.asc
powerpc.patch
|
Hi, Finally, the patch is here. Thanks to Yavor Doganov, who provided me with access to a PPC machine and was kind enough not to kick me out when I filled its disks more than once :) Thanks also go to the patient fellows on this list, especially Alex, Dmitry and Ann. OK, the patch is against RC5. Please review and apply it to HEAD. While at it, it would be good to add changes to support the mipsel port by Fabrice Aeschbacher. I need the patch(es) in HEAD before I could propose a debian package with powerpc/mipsel support, because I want to avoid any chance for implementation ID incompatibility. Thanks again, dam -- Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: marius p. <ma...@gm...> - 2006-10-14 21:52:02
|
On 10/14/06, Damyan Ivanov <da...@mo...> wrote: > > Hi, > > Finally, the patch is here. Thanks to Yavor Doganov, who provided me > with access to a PPC machine and was kind enough not to kick me out when > I filled its disks more than once :) if you need an better machine , there is openpower program to help developers who need to port on ppc http://tuxppc.rz.uni-augsburg.de/ the only issue is that is non-root account Thanks also go to the patient fellows on this list, especially Alex, > Dmitry and Ann. > > OK, the patch is against RC5. Please review and apply it to HEAD. While > at it, it would be good to add changes to support the mipsel port by > Fabrice Aeschbacher. > > I need the patch(es) in HEAD before I could propose a debian package > with powerpc/mipsel support, because I want to avoid any chance for > implementation ID incompatibility. patch works on rc5,it compiled on powerpc64 and now create_db works gpre version LI-V2.0.0.12745 Firebird 2.0 Release Candidate 5 with only one warning Version(s) for database "yachts.lnk" **unknown** (access method), version "LI-V2.0.0.12745 Firebird 2.0Release Candidate 5" I will try it to test it on an non root account mkdir -p ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64 cp -r ../gen/install/scripts ../gen/FirebirdSS- 2.0.0.12745-ReleaseCandidate5.powerpc64 cp -r ../gen/install/scripts/tarMainInstall.sh ../gen/FirebirdSS- 2.0.0.12745-ReleaseCandidate5.powerpc64/install.sh chmod a+x ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64/install.sh ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64/scripts/*sh (cd ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64; tar -C ../buildroot -czf buildroot.tar.gz . ) (cd ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64; tar -tzf buildroot.tar.gz > manifest.txt ) (cd ../gen/FirebirdSS-2.0.0.12745-ReleaseCandidate5.powerpc64; ./install.sh) --- Stop ---------------------------------------------- You need to be 'root' user to do this change make[2]: *** [install] Error 1 make[2]: Leaving directory `/home/contest/firebirdpower/firebird2/gen' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/contest/firebirdpower/firebird2/gen' make: *** [install] Error 2 > > -- developer flamerobin.org |
From: Damyan I. <da...@mo...> - 2006-10-15 15:59:47
Attachments:
signature.asc
powerpc.patch
|
marius popa wrote: > patch works on rc5,it compiled on powerpc64 > and now create_db works Thanks for testing. > gpre version LI-V2.0.0.12745 Firebird 2.0 Release Candidate 5 > with only one warning > Version(s) for database "yachts.lnk " > **unknown** (access method), version "LI-V2.0.0.12745 Firebird > 2.0 Release Candidate 5" Argh. This "**unknown**" thing is due to me forgetting to also patch jrd/utl.cpp. Updated patch attached. dam -- Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: marius p. <ma...@gm...> - 2006-10-16 12:56:49
|
On 10/15/06, Damyan Ivanov <da...@mo...> wrote: > > marius popa wrote: > > patch works on rc5,it compiled on powerpc64 > > and now create_db works > > Thanks for testing. > > > gpre version LI-V2.0.0.12745 Firebird 2.0 Release Candidate 5 > > with only one warning > > Version(s) for database "yachts.lnk " > > **unknown** (access method), version "LI-V2.0.0.12745 Firebird > > 2.0 Release Candidate 5" > > Argh. This "**unknown**" thing is due to me forgetting to also patch > jrd/utl.cpp. Updated patch attached. > I will rebuild it soon if you need an free powerpc machine for future development (at home) please propose that you want to optimize/test firebird on powerpc (until the end <http://www.ppczone.org/forums/viewtopic.php?t=841> of this month) http://projects.ppczone.org/projects.php?program=EFIKA there is one project to optimize mysql on altivec/powerpc already (it can inspire you for the text) http://www.ppczone.org/forums/viewforum.php?f=4 -- developer flamerobin.org |
From: Aeschbacher, F. <Fab...@si...> - 2006-10-16 07:58:21
|
> Finally, the patch is here.=20 Congratulations! <...> > OK, the patch is against RC5. Please review and apply it to=20 > HEAD. While at it, it would be good to add changes to support=20 > the mipsel port by Fabrice Aeschbacher. This would be kind. > I need the patch(es) in HEAD before I could propose a debian=20 > package with powerpc/mipsel support, because I want to avoid=20 > any chance for implementation ID incompatibility. >=20 > Thanks again, > dam Best regards, Fabrice Aeschbacher |
From: Damyan I. <da...@mo...> - 2006-10-16 08:59:04
Attachments:
signature.asc
|
Aeschbacher, Fabrice -- 16.10.2006 10:58 --: >> OK, the patch is against RC5. Please review and apply it to=20 >> HEAD. While at it, it would be good to add changes to support=20 >> the mipsel port by Fabrice Aeschbacher. >=20 > This would be kind. Indeed. I was wondering, how may I help the ports? If the patch looks ok (please review, it's not that huge), but noone has the time to apply it, then I guess I can apply it to CVS HEAD myself (and the accordingly adjusted mipsel one too). It only takes an admin to add me to the project. My SF username is `dbi'. Fabrice, is there any problem to order mipsel's implementation ID after powerpc? If you already have databases in production that use linux_mips=3D67 then I guess it would be better to keep this and move PPC after it. Best regards, dam --=20 Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: Aeschbacher, F. <Fab...@si...> - 2006-10-16 12:16:21
|
> Fabrice, is there any problem to order mipsel's=20 > implementation ID after powerpc? If you already have=20 > databases in production that use > linux_mips=3D67 then I guess it would be better to keep this=20 > and move PPC after it. Damyan, We are already using 'isc_info_db_impl_linux_mips =3D 67', although not yet in production. If there were a possibility, even if merging mipsel later, to keep using 'isc_info_db_impl_linux_mips =3D 67' (and 68 for linux/PPC), this would be handier for us, since it would save us a recompiling (since we are cross-compiling, you can easily imagine how many time and effort it can take for firebird - actually a few hours, and not only waiting for compiler's output :-( Best regards, Fabrice Aeschbacher >=20 >=20 > Best regards, > dam > --=20 > Damyan Ivanov Modular Software Systems > da...@mo... > phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 > mobile +359(88)856-6067 da...@ja.../Gaim >=20 >=20 |
From: marius p. <ma...@gm...> - 2006-10-16 12:36:43
|
On 10/16/06, Aeschbacher, Fabrice <Fab...@si...> wrote: > > > Fabrice, is there any problem to order mipsel's > > implementation ID after powerpc? If you already have > > databases in production that use > > linux_mips=67 then I guess it would be better to keep this > > and move PPC after it. > > Damyan, > > We are already using 'isc_info_db_impl_linux_mips = 67', although not > yet in production. If there were a possibility, even if merging mipsel > later, to keep using 'isc_info_db_impl_linux_mips = 67' (and 68 for > linux/PPC), this would be handier for us, since it would save us a > recompiling (since we are cross-compiling, you can easily imagine how > many time and effort it can take for firebird - actually a few hours, > and not only waiting for compiler's output :-( if you look in the firebird2 head<http://firebird.cvs.sourceforge.net/firebird/firebird2/src/jrd/common.h?revision=1.140&view=markup> 67 is FreeBSD/amd64 port 68 will be WIN64 (see the previous powepc porting thread) 69 will be linux/PowerPC 70 could be assigned to mips -- developer flamerobin.org |
From: Alex P. <pe...@in...> - 2006-10-16 12:48:04
|
marius popa: > > 67 is FreeBSD/amd64 port > 68 will be WIN64 (see the previous powepc porting thread) > 69 will be linux/PowerPC > 70 could be assigned to mips > I think use of this implementations list is a good idea. |
From: Damyan I. <da...@mo...> - 2006-10-16 13:26:55
Attachments:
signature.asc
|
Alex Peshkov -- 16.10.2006 15:46 --: > marius popa: >> 67 is FreeBSD/amd64 port >> 68 will be WIN64 (see the previous powepc porting thread) >> 69 will be linux/PowerPC >> 70 could be assigned to mips >> >=20 > I think use of this implementations list is a good idea. Alex, What can we do to help this list reality? dam --=20 Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: Alex P. <pe...@in...> - 2006-10-17 07:14:06
|
Damyan Ivanov: > Alex Peshkov -- 16.10.2006 15:46 --: >> marius popa: >>> 67 is FreeBSD/amd64 port >>> 68 will be WIN64 (see the previous powepc porting thread) >>> 69 will be linux/PowerPC >>> 70 could be assigned to mips >>> >> I think use of this implementations list is a good idea. > > Alex, > > What can we do to help this list reality? > If we talk about 2.0 release, I'd prefer to have it released before doing _any_ commits to cvs. In HEAD - no problems, please send patch for linux/powerPC, I will commit it. After it the same will be done with mips. I suggest to do it in 2 steps in order to avoid manually collecting to patches in single commit. |
From: Damyan I. <da...@mo...> - 2006-10-17 10:24:14
Attachments:
signature.asc
|
Alex Peshkov -- 17.10.2006 10:13 --: > If we talk about 2.0 release, I'd prefer to have it released before=20 > doing _any_ commits to cvs. In HEAD - no problems, please send patch fo= r=20 > linux/powerPC, I will commit it. After it the same will be done with=20 > mips. I suggest to do it in 2 steps in order to avoid manually=20 > collecting to patches in single commit. My intention was to go straight to HEAD. Fiddling with new port in RC5 is a bad idea (even more if considering that RC4 was intended to be "final") :) So I'm off to prepare a patches against CVS HEAD... =2E.. for powerpc and mipsel and even arm... dam --=20 Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: Alex P. <pe...@in...> - 2006-10-17 10:36:59
|
Damyan Ivanov: > My intention was to go straight to HEAD. Fiddling with new port in RC5 > is a bad idea (even more if considering that RC4 was intended to be > "final") :) > > So I'm off to prepare a patches against CVS HEAD... > ... for powerpc and mipsel and even arm... Then please review your patch to make it ready to be applied to HEAD - and let's go. With one addition - after 2.0 release it should be backported to 2.0 to be included in 2.0.1 release. I don't think it's good idea to make PPC users to wait for 2.1. And it seems to me that service release 2.0.1 will be done relatively soon. |
From: Damyan I. <da...@mo...> - 2006-10-17 13:24:56
Attachments:
signature.asc
firebird-powerpc.patch
|
Alex Peshkov -- 17.10.2006 10:13 --: > If we talk about 2.0 release, I'd prefer to have it released before > doing _any_ commits to cvs. In HEAD - no problems, please send patch for > linux/powerPC, I will commit it. After it the same will be done with > mips. I suggest to do it in 2 steps in order to avoid manually > collecting to patches in single commit. Here's the powerpc patch for HEAD. As a side benefit, I've added win64 support in utl.cpp, which seemed to be missing. After this is (eventually) applied, I'll prepare mipsel and then arm patches. Thanks, dam -- Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: marius p. <ma...@gm...> - 2006-10-23 10:09:10
|
On 10/17/06, Damyan Ivanov <da...@mo...> wrote: > > Alex Peshkov -- 17.10.2006 10:13 --: > > If we talk about 2.0 release, I'd prefer to have it released before > > doing _any_ commits to cvs. In HEAD - no problems, please send patch for > > linux/powerPC, I will commit it. After it the same will be done with > > mips. I suggest to do it in 2 steps in order to avoid manually > > collecting to patches in single commit. > > Here's the powerpc patch for HEAD. As a side benefit, I've added win64 > support in utl.cpp, which seemed to be missing. > > > After this is (eventually) applied, I'll prepare mipsel and then arm > patches. patch worked ok $patch -p1 <../firebird-powerpc.patch patching file builds/posix/prefix.linux_powerpc patching file configure.in patching file src/jrd/common.h patching file src/jrd/inf_pub.h patching file src/jrd/pag.cpp patching file src/jrd/utl.cpp $./autogen.sh --prefix=/home/contest/firebirdpower/opt --enable-debug --enable-superserver i think something changed in the HEAD make In file included from ../src/jrd/../jrd/intl_proto.h:27, from ../src/jrd/cvt.cpp:56: ../src/jrd/../jrd/../jrd/intl_classes.h:63:21: error: Charset.h: No such file or directory ../src/jrd/../jrd/../jrd/CsConvert.h: In member function 'ULONG Jrd::CsConvert::convert(ULONG, const UCHAR*, ULONG, UCHAR*, ULONG*, bool)': ../src/jrd/../jrd/../jrd/CsConvert.h:178: warning: comparison is always false due to limited range of data type -- developer flamerobin.org |
From: Damyan I. <da...@mo...> - 2006-10-23 10:18:04
Attachments:
signature.asc
|
marius popa -- 23.10.2006 13:09 --: > patch worked ok > $patch -p1 <../firebird-powerpc.patch > patching file builds/posix/prefix.linux_powerpc > patching file configure.in <http://configure.in> > patching file src/jrd/common.h > patching file src/jrd/inf_pub.h > patching file src/jrd/pag.cpp > patching file src/jrd/utl.cpp > $./autogen.sh --prefix=3D/home/contest/firebirdpower/opt --enable-debug= > --enable-superserver Thanks for testing this. > i think something changed in the HEAD > make >=20 > In file included from ../src/jrd/../jrd/intl_proto.h:27, > from ../src/jrd/cvt.cpp:56: > ../src/jrd/../jrd/../jrd/intl_classes.h:63:21: error: Charset.h: No suc= h > file or directory As far as I see, jrd/intl_classes.h should be changed to #include "CharSet.h" // note capitalization (or CharSet.h renamed to Charset.h) Either way, nothing related to the patch itself :) dam --=20 Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: Alex P. <pe...@in...> - 2006-10-23 11:49:56
|
Damyan Ivanov: > marius popa -- 23.10.2006 13:09 --: >> patch worked ok >> $patch -p1 <../firebird-powerpc.patch >> patching file builds/posix/prefix.linux_powerpc >> patching file configure.in <http://configure.in> >> patching file src/jrd/common.h >> patching file src/jrd/inf_pub.h >> patching file src/jrd/pag.cpp >> patching file src/jrd/utl.cpp >> $./autogen.sh --prefix=/home/contest/firebirdpower/opt --enable-debug >> --enable-superserver > > Thanks for testing this. > >> i think something changed in the HEAD >> make >> >> In file included from ../src/jrd/../jrd/intl_proto.h:27, >> from ../src/jrd/cvt.cpp:56: >> ../src/jrd/../jrd/../jrd/intl_classes.h:63:21: error: Charset.h: No such >> file or directory > > As far as I see, jrd/intl_classes.h should be changed to > #include "CharSet.h" // note capitalization > (or CharSet.h renamed to Charset.h) I've applied that patch, and also fixed current errors (nothing serious) in posix. |
From: Damyan I. <da...@mo...> - 2006-10-16 13:15:42
Attachments:
signature.asc
|
Aeschbacher, Fabrice -- 16.10.2006 15:17 --: > We are already using 'isc_info_db_impl_linux_mips =3D 67', although not= > yet in production. If there were a possibility, even if merging mipsel > later, to keep using 'isc_info_db_impl_linux_mips =3D 67' (and 68 for > linux/PPC), this would be handier for us, since it would save us a > recompiling (since we are cross-compiling, you can easily imagine how > many time and effort it can take for firebird - actually a few hours, > and not only waiting for compiler's output :-( I see. Unfortunately it appears 67 is already taken. What I can propose you is to wait until: 1. Mipsel patch is incorporated to HEAD with whatever implementation ID.= 2. I release debian package for firebird 1.5, with support to mipsel 3. Debian mipsel autobuilders build it for mipsel This would save you the trouble of recompiling, but with the expense of waiting (may take a couple of months) and figuring out how to proceed with .debs on possibly non-debian system of yours. Not the response you expected, sorry. dam --=20 Damyan Ivanov Modular Software Systems da...@mo... phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 da...@ja.../Gaim |
From: Aeschbacher, F. <Fab...@si...> - 2006-10-17 08:56:17
|
Hi Damyan,=20 > I see. Unfortunately it appears 67 is already taken. What I=20 > can propose you is to wait until: > 1. Mipsel patch is incorporated to HEAD with whatever=20 > implementation ID. > 2. I release debian package for firebird 1.5, with support=20 > to mipsel =20 > 3. Debian mipsel autobuilders build it for mipsel >=20 > This would save you the trouble of recompiling, but with the=20 > expense of waiting (may take a couple of months) and figuring=20 > out how to proceed with .debs on possibly non-debian system of yours. >=20 > Not the response you expected, sorry. >=20 I think this will be enough for us. Moreover, extracting from a .deb file is not really a big problem. Best regards, Fabrice Aeschbacher |
From: Dmitry Y. <fir...@ya...> - 2006-10-17 07:20:58
|
Damyan Ivanov wrote: > > Fabrice, is there any problem to order mipsel's implementation ID > after powerpc? If you already have databases in production that use > linux_mips=67 then I guess it would be better to keep this and move > PPC after it. Even if there are production databases with linux_mips=67, they can be ported to linux_mips=70 with a backup/restore cycle. Dmitry |
From: Aeschbacher, F. <Fab...@si...> - 2006-10-17 08:58:09
|
> Damyan Ivanov wrote: > >=20 > > Fabrice, is there any problem to order mipsel's implementation ID=20 > > after powerpc? If you already have databases in production that use > > linux_mips=3D67 then I guess it would be better to keep this and = move=20 > > PPC after it. >=20 > Even if there are production databases with linux_mips=3D67,=20 > they can be ported to linux_mips=3D70 with a backup/restore cycle. Thanks for this info, I didn't knew. Fabrice |